feat: new core api - Mixin #6375
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.
What is the current behavior?
A Stencil component can only
extend
from another, single class.Dynamic, mixin style behaviour (as outlined here) being hard in Stencil as it relies on static analysis to extract component meta.
GitHub Issue Number: #3162 I think?
What is the new behavior?
A new core
Mixin
helper function to extend from. This provides a predictable pattern to pull apart for Static analysis.The function accepts mixin-factory-functions as arguments and the end result is typed appropriately with all relevant Stencil-related meta being merged correctly.
e.g.
Documentation
stenciljs/site#1545
Does this introduce a breaking change?
Testing
Other information