FriendsOfSymfony/FOSUserBundle — Issue #450: Symfony 2.1 requirement for FOSUserBundle 1.2
Author: stof
Created: 2011-12-16 13:29:02+00:00
State: open
Labels: RFC

I would like to bump the Symfony requirement to 2.1 (i.e. the current master branch) for FOSUserBundle 1.2. Here is a summary of the issues [scheduled for 1.2](https://github.com/FriendsOfSymfony/FOSUserBundle/issues?sort=created&direction=desc&state=open&page=1&milestone=3):

* **Dropping the encoder** (#395 and #388): done and compatible with Symfony 2.0
* **Removing our hacky way to translate form labels** (#292 and #301): I implemented the needed feature in Symfony 2.1 to achieve it. If we want to keep the compatibility with 2.0, the Form component is flexible enough to implement the feature using its extension points (with a little work for the end-user to change the form theme). Such forward compat is out of the scope of FOSUserBundle IMO but it could be done in [SimpleThingsFormExtraBundle](https://github.com/simplethings/SimpleThingsFormExtraBundle) and linked from the doc.
* **Improving the current password validation** (#381): solved by using the new core constraint available in 2.1 (no compatibility with 2.0)
* **Replace the uniqueness validators** (#449): Requires the change done in Symfony 2.1 to load these constraints only when the appropriate bundle is loaded (to have the classes). This requires updating the different bundles as only DoctrineBundle uses the new feature currently.

The other issues don't add requirements for Symfony currently (the point about exceptions is not yet fixed in Symfony at all)