ORO Meetups - Symfony2 Worst Practices

1. Symfony Worst Practices
Worst Practices
Michael Sulima
msulima@magecore.com

2. Symfony Worst Practices
Don’t use this tool

3. Symfony Worst Practices
Fat Stupid Ugly Controllers

4. Symfony Worst Practices
Fat Stupid Ugly Controllers
■ Use single responsibility principle also for controller actions
■ Do not start coding in controllers
■ Do not create forms in controllers
■ Extract your shared methods or avoid them at all
■ Go the test driven way

5. Symfony Worst Practices
Doctrine likes memory

6. Symfony Worst Practices
Doctrine likes memory
■ Avoid Object Hydration when handling many entities
■ Don’t load the whole entity if you only need reference to it
■ Do not flush inside cycles

7. Symfony Worst Practices
Fat DI Container
■ Controllers as services
■ Single use forms
■ Do not create parameter if you will never needed to change that value

8. Symfony Worst Practices
Circle dependency between
bundles

9. Symfony Worst Practices
Don’t inject DIC into services

10. Symfony Worst Practices
Using Object Manager
■ Do not inject Object Manager into entities
■ Do not inject Object Manager into services

11. Symfony Worst Practices
Binding to the Environment

12. Symfony Worst Practices
Using data in form constructors

13. Symfony Worst Practices
Bibliography
■ http://richardmiller.co.uk/2012/10/31/symfony2-trimming-fat-from-controllers/
■ http://labs.octivi.com/mastering-symfony2-performance-doctrine/
■ http://knpuniversity.com/screencast/question-answer-day/controllers-services

14. Symfony Worst Practices
Q & A

15. Symfony Worst Practices
No?