feat(compiler): CustomStateSet support#6574
Merged
johnjenkins merged 10 commits intomainfrom Jan 29, 2026
Merged
Conversation
customStates supportCustomStateSet support
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
As per the original issue #6285 - Stencil removed the barrier for devs to use
CustomStateSet, however - it doesn't document their use within components.What is the new behavior?
A new declarative api for documenting custom states has been added to the
AttachInternalsdecorator:Results in:
Runtime:
Build time:
Custom-elements-manifest:
JSON docs:
readme.md
Rationale
I didn't want to invoke too much Stencil magic; I believe this strikes a balance between quality-of-life and not straying too far from native APIs. After initialisation, users are free to use their
internalsas per any documentation found on the web.Additionally, this pattern is extendible if we want to absorb any other meta around
ElementInternalslater e.g.:Documentation
TODO
Does this introduce a breaking change?
Testing
Unit and WDIO
Other information