Commite004661

authored and

committed

Bundle names should not be placed in literals

1 parent38b1292 commite004661Copy full SHA for e004661

File tree

-2

lines changed

-2

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -259,7 +259,7 @@ Extending Bundles`
`259`	`259`
`260`	`260`	If you follow these conventions, then you can use:doc:`bundle inheritance</cookbook/bundles/inheritance>`
`261`	`261`	`to "override" files, controllers or templates. For example, you can create`
`262`		-a bundle -``AcmeNewBundle`` - and specify that it overrides AcmeDemoBundle.
	`262`	`+a bundle - AcmeNewBundle - and specify that it overrides AcmeDemoBundle.`
`263`	`263`	When Symfony loads the ``AcmeDemoBundle:Welcome:index`` controller, it will
`264`	`264`	first look for the ``WelcomeController`` class in AcmeNewBundle and, if
`265`	`265`	`it doesn't exist, then look inside AcmeDemoBundle. This means that one bundle`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -293,7 +293,7 @@ have seen so far. All the code you write for your application is organized in`
`293`	`293`	`bundles. In Symfony2 speak, a bundle is a structured set of files (PHP files,`
`294`	`294`	`stylesheets, JavaScripts, images, ...) that implements a single feature (a`
`295`	`295`	`blog, a forum, ...) and which can be easily shared with other developers. As`
`296`		-of now, you have manipulated one bundle,``AcmeDemoBundle``. You will learn
	`296`	`+of now, you have manipulated one bundle, AcmeDemoBundle. You will learn`
`297`	`297`	more about bundles in the:doc:`last part of this tutorial</quick_tour/the_architecture>`.
`298`	`298`
`299`	`299`	`.. _quick-tour-big-picture-environments:`

Comments

(0)