Gear Up for OroPlatform 4.1 LTS. Dependency Injection Improvements Overview and Practical Examples.
0 likes281 views
The document provides an overview of the improvements in dependency injection for OroPlatform 4.1 LTS, emphasizing the transition to Symfony 4.4 LTS. Key features include private services, autowiring, and class names used as service IDs, which simplify service configuration. The upgrades also enhance developer experience by reducing the need for complex configurations and introducing automation in service management.
Gear Up for OroPlatform 4.1 LTS. Dependency Injection Improvements Overview and Practical Examples.
- 1. Gear Up for OroPlatform 4.1 LTS. Dependency Injection Improvements
- 2. www.oroinc.com Andrey Yatsenko Passionate about Symfony & DX - Trainer - Developer - Developer Advocate - Mentor of Advanced PHP course on GeekHub - Symfony 3 Certified Developer (Expert)
- 4. Service Container - An object that knows how to instantiate all the application services - Lazy loaded - Frozen after build
- 5. PSR 11 & Symfony Container
- 6. DIC knows how to create the service
- 8. There are 8000 services in OroCommerce CE application
- 9. Symfony Upgrade OroPlatform 3.1 LTS Symfony 3.4 LTS OroPlatform 4.1 LTS Symfony 4.4 LTS
- 10. Symfony Upgrade = New features
- 11. Symfony Upgrade = New features + Dropped deprecations
- 12. Biggest Changes to DI - Private Services - Class name as service id - Autowiring - Autoconfiguration - Controllers as services - No Bundles * Most of the listed features were introduced in Symfony 3.3 - Yaml syntax improvements: - _defaults - autowiring - autoconfiguration - !tagged_iterator - !iterator - !service_locator - !returns_clone - !service
- 13. Dropped Service Class Parameters in Oro Bundles
- 14. 3rd Party Deps Still Use Service Class Parameters - akeneo_batch - doctrine - fos_js_routing - hwi_oauth - jms_serializer - knp_menu - nelmio_api_doc - snc_redis - stof_doctrine_extensions - etc.
- 15. Class Names as Service Ids Before
- 16. Class Names as Service Ids After
- 17. Two Services with the Same Class
- 18. Short Syntax for Services Without Deps
- 19. !service for Anonymous Services
- 20. Autowiring - Only configure the parts that you need. Most configuration is automated. - Aims to automate configuration without magic.
- 21. Autowiring
- 23. Autowire Setters
- 25. Debug Autowiring from CLI Class names are links to PhpStorm O_O
- 26. Public and Reusable Bundles Public bundles should explicitly configure their services and not rely on autowiring.
- 28. !tagged_iterator for Ordered Collection of Services
- 29. !tagged_locator for Indexed Collection of Services
- 31. Autoconfiguration on File Level
- 32. Autoconfiguration on Global Level
- 33. Unbinding Circular References - Public service + container injection - Lazy service - Oro Service Link
- 34. Service Locators
- 35. Service Locators
- 37. Private Services by Default Some are still public: - Controllers - Commands - Services fetched from Container directly - Lazy Services - Those that were hard to refactor
- 38. Workarounds to Save Upgrade Time In ContainerAware migrations all*oro* services are still public https://github.com/oroinc/platform/tree/ master/src/Oro/Bundle/MigrationBundle/ DependencyInjection/Compiler
- 39. Controllers as Services - Constructor injection - Arguments injection - Service Locator
- 42. Conclusion - Symfony 3.3 DI improvements can now be fully used - Services configuration is now much easier in Yaml - Less reasons to create a Compiler Pass - Autowiring is not recommended - DX was significantly improved in OroPlatform 4.1 LTS, thanks to Symfony 4.4 LTS
- 43. Q&A