Using ComponentPublicInstance with template refs #2251
Merged
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.
#2210 suggested using
ComponentPublicInstance
instead ofInstanceType
for template refs:The first generic argument passed to
ComponentPublicInstance
should be the props, so the usage shown above isn't really correct.InstanceType
may be changed toComponentInstance
in future, see #1543, but currently this isn't available.However,
ComponentPublicInstance
can be used as a base type in cases where the exact type of the component isn't available. This will only expose the properties that are common to all component instances, such as$el
.