Skip to content

Commit 58bb3c5

Browse files
Ana Cicconiweaverryan
Ana Cicconi
authored andcommitted
overriding 3rd party bundles
1 parent c9c6a97 commit 58bb3c5

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

best_practices/creating-the-project.rst

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,13 @@ Symfony documentation uses the AppBundle name.
110110
There is no need to prefix the AppBundle with your own vendor (e.g.
111111
AcmeAppBundle), because this application bundle is never going to be
112112
shared.
113+
114+
.. note::
115+
116+
Another reason to create a new bundle is when you're overriding something
117+
in a vendor's bundle. For instance, if you have to override an action of
118+
the FOSUserBundle, then you should create a UserBundle that would be used
119+
only for this purpose.
113120

114121
All in all, this is the typical directory structure of a Symfony application
115122
that follows these best practices:

0 commit comments

Comments
 (0)