-
-
Notifications
You must be signed in to change notification settings - Fork 112
added {include with blocks} as a successor to {includeblock} #152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I hate the syntax. Also include related stuff are changed way too often -> deeper analysis is required. |
|
Do you have a better idea about syntax? |
|
Not yet. I don't want to rush this change just to change it in two weeks again. |
|
I don't know what are you talking about. |
|
The syntax |
|
|
dc17ef3 to
7550eb3
Compare
118e433 to
2f2e445
Compare
beacf44 to
ee18dfc
Compare
e83378c to
1ed4097
Compare
91a8964 to
d4f519e
Compare
04cdb42 to
1870016
Compare
f1158da to
7957380
Compare
|
Changed to |
There are use cases where
{includeblock}is useful and cannot be substituted by{import}. But the name{includeblock}is misleading. This is attempt to solve it by more understandable{include with blocks 'file.latte'}Cons: this introduces syntax which is not common in Latte.
https://forum.nette.org/cs/26699-latte-vypis-bloku-do-include