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

  • Mastering Symfony
  • Sohail Salehi
  • 263字
  • 2021-07-16 11:28:59

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
主站蜘蛛池模板: 遂溪县| 黑水县| 赤水市| 夏河县| 房产| 左贡县| 彩票| 平江县| 淮南市| 吴旗县| 诸城市| 陵川县| 兴文县| 来凤县| 太和县| 昌吉市| 东至县| 双牌县| 余庆县| 民勤县| 渝北区| 翁牛特旗| 米林县| 昆山市| 安岳县| 明星| 巨野县| 于田县| 柳林县| 枞阳县| 鄢陵县| 宁津县| 虞城县| 乾安县| 闵行区| 天全县| 临澧县| 茌平县| 三门县| 邵东县| 宾川县|