-
-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
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
WIP: Reintroduce FOSUserBundle #656
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request passes validation.
Depends on FriendsOfSymfony/FOSUserBundle#2708 |
Initially added in symfony#270 and reverted in symfony#655
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request passes validation.
We are waiting for FriendsOfSymfony/FOSUserBundle#2708 |
@@ -0,0 +1,10 @@ | |||
fos_user: | |||
db_driver: no_driver # valid values are 'orm', 'mongodb' and 'couchdb' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not yet supported.
I think we have a problem here. One side, we don't want to pre-config the db_driver to orm. But at the other side, we are includin a User entity that uses ORM annotations, that requires doctrine/orm. I think we have two options right now. One, set default db_driver to orm, and configure a the recipe according. The other, create a new meta-package, fosuserbundle-orm, that requires fosuserbundle and doctrine-bundle, and create a new recipe for this new meta-package that can be configured to use orm as db_driver. What do you think? |
Initially added in #270 and reverted in #655