Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Commite00a3a2
committed
feature#8608 Add Best Practice guideline for partials/include (timonf, weaverryan)
This PR was submitted for the master branch but it was merged into the 2.7 branch instead (closes#8608).Discussion----------Add Best Practice guideline for partials/includeHi there,I was wondering if there is no Best Practice guide for partials/includes. So I would recommend to use a single prefixed underscore to determine such partials easily like in the Symfony demo application:https://github.com/symfony/demo/tree/master/templates/blogI saw often other solutions like `@SomeBundle:Partials/post_form.html.twig`. But I like the approach from the Symfony demo application, so it should be a Best Practice guideline :)Regards,TimonCommits-------bbd705d Added Best Practice guideline for partials/include1 file changed
+9
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
53 | 53 | | |
54 | 54 | | |
55 | 55 | | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
56 | 65 | | |
57 | 66 | | |
58 | 67 | | |
| |||
0 commit comments
Comments
(0)