Replies: 2 comments
-
|
I would like the ability to specify the priority of an extension (the higher the priority, the earlier an extension is being checked for a specific modifier/block/etc function). This way you can overwrite the internal functions with your own implementation if needed. Maybe determine the corresponding extension for a modifier at compiletime instead of at runtime (now when a modifier is called it has to look trough all the extensions everytime iirc) And maybe add a benchmark suite in CI so we can see what a release does for the performance of the engine? :D |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @wisskid for this initiative! The Tiki community will help for testing as we did for Smarty 5: #920 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It's been 3 years since work on Smarty v5 started. Time to plan for Smarty v6! Work is already underway, but I'd like the input of the community on what you think we should add and what we should leave out.
Some highlights I'd like to propose:
nocacheblocks and attributes to a native{cache}...{/cache}block see Who is using nocache? #853 and Drop support for {nocache} block and nocache attribute #1199$smarty.block.childas this will greatly simplify the application logic and prevents potential loops when used together with$smarty.block.parentAny thoughts? What would you like to see added to this list?
Beta Was this translation helpful? Give feedback.
All reactions