When to Use General vs. Specific Symfony Bundles for Shared Code?

Symfony2 Conceptual Issue: General Bundles vs. Specific Ones

When organizing a complex Symfony2 application, there are considerations to be made regarding the structure of bundles and the organization of shared code. Questions commonly arise on the best practices for creating general versus specific bundles.

General Bundles for Frontend and Backend

The use of general bundles for frontend and backend, despite their lack of controllers, can be appropriate in certain scenarios. However, it's essential to carefully consider the organizational benefits and potential maintenance challenges.

Layouts in Bundles or Application Resources

While layouts are commonly stored in the app/Resources/views/ directory, exceptions exist for specific use cases. If layouts are heavily common to multiple bundles, such as base layouts, it can make sense to place them in bundles for centralization.

RootBundle for Shared Functionality

Creating a RootBundle to contain application-wide functionality can be beneficial for centralizing shared code. However, alternative approaches include creating specific bundles for each functionality, such as PaginatorBundle, DateDisplayerBundle, etc. The choice depends on the complexity and reusability of the shared code.

The above is the detailed content of When to Use General vs. Specific Symfony Bundles for Shared Code?. For more information, please follow other related articles on the PHP Chinese website!