Skip to content

bundles - add reason why they are not recommended #20188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 3, 2024
Merged

bundles - add reason why they are not recommended #20188

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions best_practices.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,8 @@ values is that it's complicated to redefine their values in your tests.
Business Logic
--------------

.. _best-practice-no-application-bundles:

Don't Create any Bundle to Organize your Application Logic
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
2 changes: 1 addition & 1 deletion bundles.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ The Bundle System
.. caution::

In Symfony versions prior to 4.0, it was recommended to organize your own
application code using bundles. This is no longer recommended and bundles
application code using bundles. This is :ref:`no longer recommended <best-practice-no-application-bundles>` and bundles
should only be used to share code and features between multiple applications.

A bundle is similar to a plugin in other software, but even better. The core
Expand Down
Loading