You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extensions will work similarly to how they do now, they'll just receive the Engine object and can then configure it accordingly. Very similar to how service providers work.
Extensions will be very powerful and I want to try and implement much of functionality via extensions in an attempt to eat my own dog food and showcase the power of extensions.
Here is a list of standard extensions that I want to support:
Still in the works is the TemplateContext and how to provide functions inside of the template itself. Do we use something like macros #134 or keep with a design similar what plates has now?
- Simplied v4 layout and moved core features into extensions
- Moved the docs to docv3
- Plates now only has a few core concepts: Templates, References, RenderTemplate, and Composers.
Everything else was removed.
- Added Data Extension #186
- Added LayoutSections Extension #171
- Added Folders Extension #182
- Added RenderContext Extension
- Added Path Extension
- Added ability for Static File templates #187
- Basically broke all of tests ;p
Signed-off-by: RJ Garcia <rj@bighead.net>
Extensions will work similarly to how they do now, they'll just receive the Engine object and can then configure it accordingly. Very similar to how service providers work.
Extensions will be very powerful and I want to try and implement much of functionality via extensions in an attempt to eat my own dog food and showcase the power of extensions.
Here is a list of standard extensions that I want to support:
The text was updated successfully, but these errors were encountered: