Replies: 2 comments 1 reply
-
I am open to making this library useful to other templating engines. Feel free to create a PR with a proposal how to tackle this. |
Beta Was this translation helpful? Give feedback.
1 reply
-
PR is now merged and will be included in the upcoming 2.2.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What do you think about that idea? It would be useful for some of the reflection-free templating options that are becoming popular (JStachio, Rocker, JTE), and provides flexibility if the controller method already knows how to resolve a view. The implementation wouldn't need to change any public APIs, but the internals of how the templates are stored (e.g. use
Object
instead ofString
or introduce a new wrapper object, a bit likeModelAndView
).ModelAndView
might not be a bad choice even - each template might conceivably have its own model, and merge with the request-level model at rendering time.Beta Was this translation helpful? Give feedback.
All reactions