Custom User Method

Instead of $uri .= sprintf('?size=%dx%d', $size, $size); you can do $uri .= sprintf('?size=%1$dx%1$d', $size);. This removes the duplication of the $size arguments.

Thanks for sharing it!

You should not write your robohash-url in your entity, please use a view-helper instead, god damn it :-p

Hey Szabolcs!

That's definitely a valid way to handle it :). Because I don't need any service logic, I can use the simpler solution and put it in the entity. But it *is* true that if, later for some reason, we need to refactor this logic to require a service, we'll need to do more work (update our templates) to make that change. So better organization now would make that possible situation easier later.

Cheers!

public function getAvatarUrl(string $size = null)

I think you meant int here, not string

You're right! That's our fault. I'm gonna fix it right now :)
Thanks for letting us know!

{{ app.user.username }}
Where does .user come from? You might have explained it, but I can't remember. Is it coming from the User class?
Is it guessing wether .user matches the User class?

Hey Farry7,

It looks like you've missed some information following this course :). That "app" is a special global Twig variable, it's an object of AppVariable class, that has some useful methods, one of them is "getUser()". But Twig is smart enough to call getter methods behind the scene when you call just {{ app.user }}, i.e. behind the scene Twig will call that getUser method that will return the current logged in user or null. Basically, you can manually specify that method like {{ app.getUser() }}, but usually everybody shorts that call to just {{ app.user }{.

Hope this is clear for you now.

Cheers!

Ok, so what you can do is to check both configurations and look if something relevant is different. If you run php -i in your terminal you will see all PHP settings

Hey @disqus_uUZdE4XYyx

Does it work when you run your application through the browser? If you only got that error via a console command it's very likely that it's running a different php executable.

Cheers!

I don't know if this is a good idea or not, but I ended up passing the user to the view, in this way I've got both autocompletion in PHPStorm and a shorter way to get the user data:

return $this->render('account/index.html.twig', [
    'user' => $this->getUser()
]);

In the view:

{{ user.firstName }}

Hey Duilio P.

The only downside I see to your approach is that you could pass a different User object to your template and it would look like as the logged in user. About autocompletion, I have the same problem, I believe the Symfony plugin has a bug on it.

Cheers!

Thanks, you're right :) I'll remember to add a test for that or to use app.user instead.

Well PHPStorm does autocomplete the app.user variable inside of twig, but it doesn't do it any further (it can't autocomplete/doesnt show anything beyond app.user.) is that normal?

It behaves exactly the same for me. I believe there is a way to tell PhpStorm the instance of which class is that varaible but I'm not sure how. Probably you can talk to the developers of the Symfony plugin about this.

Cheers!

By starting > v5, FontAwesome starting tag is "fab" but not "fa". :)
Please, fix it inside the html.twig files :)

https://fontawesome.com/ico...

Regards.

Hey Abelardo L.!

You're right! Well, we're using FontAwesome 4 in this tutorial - that's why we have the fa tag :). But if you're using Font Awesome 5, then you're totally right: fab fa-twitter.

Thanks!

In the getAvatarUrl method, why do you call `$this->getEmail()` instead of `$this->email`?

Hey Tom!

No particular reason. In general, I tend to like to *always* call my getters, in the (rare) event that I add some sort of logic in that method that changes the return value in some way I want, or maybe throws an exception if something isn't right. It just gives me that flexibility if I need it, which is honestly rare in these very simple entity classes. For me, both are fine :).

Cheers!