8000 Minor tweak to remove FOSUserBundle example and replace with a link t… · symfony/symfony-docs@c24862b · GitHub
[go: up one dir, main page]

Skip to content
Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit c24862b

Browse files
committed
Minor tweak to remove FOSUserBundle example and replace with a link to the doc about this
1 parent e687f5d commit c24862b

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

best_practices/creating-the-project.rst

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -114,9 +114,7 @@ Symfony documentation uses the AppBundle name.
114114
.. note::
115115

116116
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.
117+
in a vendor's bundle (e.g. a controller). See :doc:`/cookbook/bundles/inheritance`.
120118

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

0 commit comments

Comments
 (0)
0