We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FOSUserBundle shouldn't be required as it's intrusive, it's the final developper choice
We can keep the parts of code related to FOSUserBundle but in the form of a bridge. Guard seems to be the next (current?) standard: http://symfony.com/doc/current/security/guard_authentication.html
There isn't so much of features to have in mind when refactoring this but it should be available natively and easy to override:
Then, we won't require friendsofsymfony/user-bundle but suggest it in composer.json.
require
friendsofsymfony/user-bundle
composer.json
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
FOSUserBundle shouldn't be required as it's intrusive, it's the final developper choice
Resolution Ideas
We can keep the parts of code related to FOSUserBundle but in the form of a bridge.
Guard seems to be the next (current?) standard: http://symfony.com/doc/current/security/guard_authentication.html
There isn't so much of features to have in mind when refactoring this but it should be available natively and easy to override:
Then, we won't
require
friendsofsymfony/user-bundle
but suggest it incomposer.json
.Related to
The text was updated successfully, but these errors were encountered: