We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent c9c6a97 commit 58bb3c5Copy full SHA for 58bb3c5
best_practices/creating-the-project.rst
@@ -110,6 +110,13 @@ Symfony documentation uses the AppBundle name.
110
There is no need to prefix the AppBundle with your own vendor (e.g.
111
AcmeAppBundle), because this application bundle is never going to be
112
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.
120
121
All in all, this is the typical directory structure of a Symfony application
122
that follows these best practices:
0 commit comments