I watched your videos about symfony. The courses on authorization and messenger turned out to be very interesting and useful. I hope that you will release a big course on Symfony Workflow.
AbstractGuardAuthenticator is deprecated, are you planning to make these again for symfony 5.3 ? It is gonna be really usefull and there is no content about that on youtube. Thanks for all of this by the way.
@@GaryClarkeTech I'll stick on symfony v5.2.99 for know then even though this video is a value for junior devs like me who is new on symfony. Thanks for your effort.
@@pawecyrklaf4729 ja to co jakiś czas wracam i oglądam materiały aby zobaczyć co nowego przygotowali ;) aczkolwiek już po kilku latach pisania w Symfony, więcej się czerpie z dokumentacji i stackoverflow ;D
@@garethfoxtrot5722 Mam dokładnie tak samo, jak coś szukam to dokumentacja lub stackoverflow, bo w tych kursach nie ma rzeczy, które po kilku latach pisaniach są nowością :D
@@garethfoxtrot5722 Ogólnie to nic szałowego tam już nie ma, dobre miejsce dla kogoś kto dopiero zaczyna z Symfony. Niestety nie które kursy oparte są o SF2, więc trochę nie aktualne :D
It would be super cool if you would have time to make a course about Symfony API Platform. The one on symfony casts about cheeses is absolutely ridiculous and childish. I would also gladly buy a course like that on Udemy! Anyways ... Great content!!!
Thanks Mihai...I appreciate it. I'm currently planning a Symfony API course..it will be paid but I'm gonna put some of the content on RU-vid such as API authentication for example
Use a User repository to find the users you wish to display: www.doctrine-project.org/projects/doctrine-orm/en/2.9/reference/working-with-objects.html#by-simple-conditions Send the users to your view from your controller in a render method: symfony.com/doc/current/controller.html Then you can loop over your users and display the info about them in a twig template: {% for user in users %} {{ user.username }} {% endfor %}
Hey Gary hope you don't mind, I have another question for you 😅 Do you know why the roles are prefixed with "ROLE_" string? Wouldn't it make more sense to call them something like "CAN_VIEW_ITEM", "IS_RESPONSIBLE_FOR_SOMETHING", etc.
I'm afraid you've got no choice in that...that's how the core functionality was written, it's not something which you or me could change. The prefix is checked with each request and so having a fixed value makes sense I think.
hi thank you for this wonderful tutorial i have one question fosuserbundle handle all the registration, login, reset password and more important it has good access control and it is easy to use. 1. don't you recommend to use fosuserbundle instead? i know that it is not maintenance anymore. 2. but is it going to be a problem in a project that it does not maintenance? thank you for answering
Thanks for watching...I appreciate it. I never use anything that is no longer maintained and I don't think I've ever worked on a project that hasn't required maintenance. I'd always advise to follow best practices and stick with well maintained software.
Hey Gary, thank you for your tutorials! I was wondering is there a way to have multiple firewalls? One for customers and another for administrators, obviously those two being two separate entities
You're welcome Anton, cheers. Yes, you can have multiple firewalls but it's not recommended...I think even the docs recommend against this or maybe it's something I heard Ryan Weaver saying. Any disctinctions you need to make between customers and admins can be done with one firewall using roles and permissions. I'd say keep it simple.
@@GaryClarkeTech Yeah I've already implemented that and then saw your response 😅 Is there any arguments against that? Because to me it seems very neat, can't find drawbacks in that setup.