Distinguish instance- from direct-invokable types #59
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 the two types of resolvable value are
Invokable<T>
andnew () => Invokable<T>
. This largely works well, with one main exception: it makes{{this}}
look like an invokable value in component templates, since the instance type is itselfInvokable<T>
.To fix this, we can distinguish between the normal case of invokable values that are wrapped in a constructor (which covers user-defined components, helpers and modifiers) and "direct invokable" values that are largely used internally to represent intrinsics like
{{each}}
and{{fn}}
.Plain function usage, as in GlimmerX, is unaffected by this change.