|
1 | | - |
2 | 1 | The Architecture |
3 | 2 | ================ |
4 | 3 |
|
5 | | -You are my hero! Who would have thought that you would still be |
6 | | -here after the first three parts? Your efforts will be well |
7 | | -rewarded soon. The first three parts didn't look too deeply at |
8 | | -the architecture of the framework. Because it makes Symfony2 |
9 | | -stand apart from the framework crowd, let's dive in to the |
| 4 | +You are my hero! Who would have thought that you would still be here after the |
| 5 | +first three parts? Your efforts will be well rewarded soon. The first three |
| 6 | +parts didn't look too deeply at the architecture of the framework. Because it |
| 7 | +makes Symfony2 stand apart from the framework crowd, let's dive in to the |
10 | 8 | architecture now. |
11 | 9 |
|
12 | 10 | Understanding the Directory Structure |
@@ -240,11 +238,11 @@ specific configuration file: |
240 | 238 | Extending a Bundle |
241 | 239 | ~~~~~~~~~~~~~~~~~~ |
242 | 240 |
|
243 | | -In addition to being a nice way to organize and configure your code, a bundle can |
244 | | -extend another one. Bundle inheritance allows you to override |
245 | | -any existing bundle to customize its controllers, templates, and any of its files. |
246 | | -This is where the logical names come in handy, because they abstract where |
247 | | -the resource is actually stored. |
| 241 | +In addition to being a nice way to organize and configure your code, a bundle |
| 242 | +can extend another one. Bundle inheritance allows you to override any existing |
| 243 | +bundle to customize its controllers, templates, and any of its files. This is |
| 244 | +where the logical names come in handy, because they abstract where the resource |
| 245 | +is actually stored. |
248 | 246 |
|
249 | 247 | For controllers, Symfony2 will automatically choose the right file according |
250 | 248 | to the bundle inheritance tree. |
|
0 commit comments