Adding RenderContext trait so users can provide access to arbitrary structs without converting it all into a Value #929
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think that this will help users expose more extensive data structures to Tera without needing to recursively convert to a
Value
when rendering.The existing api should still be compatible because both
Context
and any immutable borrow of aRenderContext
will implementRenderContext
so the render calls in tera.rs should still work with&Context
.I don't think I've changed any logic for the
Context
rendering. It is all confined to theRenderContext
trait definition now though.