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
After thinking a bit on #155 and writing it up in the docs, I think it'd be nice to, much like how it's possible in vanilla Thymeleaf, for th:insert/th:replace attribute processors (http://www.thymeleaf.org/doc/tutorials/3.0/usingthymeleaf.html#parameterizable-fragment-signatures), it'd be nice to be able to pass values from child templates up to their parent layouts in this manner, doing away with the need for th:with attribute processors on the same element (even though I won't remove support for that either, it'll just be another option), eg:
<html>
...
<pth:text="${greeting}"></p><!-- You'll end up with "Hello!" in here -->
Some things to think about for whether this is feasible:
I'd be unable to enforce parameter correctness for full template references because there's nowhere to specify a signature on a template
So parameters used in layout:decorate would require a name
Otherwise everything is as expected for layout:insert and layout:replace as they behave just like Thymeleaf's equivalent processors (in fact, I believe these processors already support fragment signatures)
The text was updated successfully, but these errors were encountered:
After thinking a bit on #155 and writing it up in the docs, I think it'd be nice to, much like how it's possible in vanilla Thymeleaf, for
th:insert
/th:replace
attribute processors (http://www.thymeleaf.org/doc/tutorials/3.0/usingthymeleaf.html#parameterizable-fragment-signatures), it'd be nice to be able to pass values from child templates up to their parent layouts in this manner, doing away with the need forth:with
attribute processors on the same element (even though I won't remove support for that either, it'll just be another option), eg:Parent/layout template:
Some things to think about for whether this is feasible:
layout:decorate
would require a namelayout:insert
andlayout:replace
as they behave just like Thymeleaf's equivalent processors (in fact, I believe these processors already support fragment signatures)The text was updated successfully, but these errors were encountered: