官术网_书友最值得收藏!

Custom bundles versus AppBundle

When we use AppBundle as a code base, the app/ directory of our project can be seen as part of AppBundle. Sure, it has other files and folders that take care of other bundles available in the /vendor directory, for example, but we can benefit a lot from the app/ folder.

For example, if you look at the MyBundle/Resources folder, you will find two subfolders named Resources/config/ and Resources/views/, which hold service definitions (and other required settings in the future) and template files for that bundle.

However, with AppBundle, we already have a folder named app/, so conveniently, we can use the available app/config for our configuration needs and app/Resources/views for our templates. Using this approach, referencing these files are much easier.

Compare the render() method in indexAction() of each controller. In the AppBundle controller, we simply referenced the template file without mentioning the name of the bundle. When there is no bundle name, Symfony by default looks in the app/Resources/views directory to find the required template:

return $this->render('default/index.html.twig');

To check the contents of the app/Resources/views directory use the following command:

$ tree app/Resources/views/
app/Resources/views/
├── base.html.twig
└── default
 └── index.html.twig

In MyBundle, we have to mention the bundle name in the reference:

return $this->render('MyBundle:Default:index.html.twig');

Note

Did you notice the tests/ folder that Symfony created in the root of the project? We can use it to write tests for AppBundle.

We got two elements of MVC so far: Controller and View. Let's have a look at the big picture that we have now:

Custom bundles versus AppBundle
主站蜘蛛池模板: 天津市| 白朗县| 汤阴县| 广饶县| 兴城市| 宣汉县| 长沙县| 铁岭市| 双桥区| 鹤峰县| 手游| 万山特区| 尉氏县| 沁源县| 兰考县| 玛纳斯县| 沙田区| 尚志市| 大关县| 海淀区| 分宜县| 梁河县| 海阳市| 娄底市| 黄大仙区| 长汀县| 吉木萨尔县| 洪泽县| 青川县| 仪陇县| 都兰县| 南华县| 夹江县| 大渡口区| 自治县| 枣阳市| 衡南县| 万荣县| 军事| 霍城县| 铜梁县|