enable passing Template objects to BlazeLayout.render #77
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.
Currently, if you pass a template object in (instead of a string) as the layout to BlazeLayout.render, you receive an error because blaze-layout attempts to lookup the template by name.
If you pass in the template object (instead of a string) as data to BlazeLayout.render, the template doesn't render because the ReactiveDict stringifies the object.
Adding a simple check for layout template objects and switching to ReactiveMap for the data keeps the existing functionality for strings while allowing Templates to be passed in.
This can be used for vanilla Blaze, although its primarily useful for my Blaze Modules package where Blaze templates can be imported:
With vanilla Blaze: