Symfony2, what I think is still left to do
Note: This article was originally published at Planet PHP
on 19 April 2011.
The goal of this blog post is to number one serve me as a todo list of stuff that I personally think needs to be fixed before Symfony2 can be released. Hopefully it will also entice some people to help out with these tasks. I am focusing on the medium to large tasks. There are of course still a fair number of smaller fixes that need to be applied.
- finish form layer rewrite (and close the many related tickets and PRs)
- attempt to automatically determine service scopes
- clean up Security component exceptions to make it easier to determine what exception messages contain sensitive information
- switch Security/Validation components to using message key's rather than full sentences
- fix cache warming for functional tests
- Assetic documentation
- Something similar to the Jobeet tutorial
- FrameworkExtra and SecurityExtra annotation issues when using Doctrine Common master
- Interface injection overriding
- Various minor issues that seem to be plaguing ESI support (though actually these might be worked out by now)
- Doctrine2 EntityManager rollback not playing nicely with the DIC
- Adding a DIC aware Serializer
- Better support for SSL'ed urls and assets
- Make sure core works nicely with FOSRestBundle, like small changes to enable flexible format negotiations and truly optional route parameters
Anything critical I forgot? Anyone wondering how to help ask away :)