Use Blaze._getTemplate to allow resolving into Blaze Components #10
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.
With meteor/meteor@eff8016 there is now a
Blaze._getTemplate
function which is better to use than accessingTemplate[...]
directly. The reason is that then packages like Blaze Components can overrideBlaze._getTemplate
to provide resolving into components instead of bare templates.I am not 100% sure if:
is the best way to get current template instance, maybe it is available already somewhere in this code-path? But it should work this way as well. But I do not like access to global variables which
Template.instance
uses internally. So if you know of any better way to access current template instance at that code point, that would be great.