chore: exclude focus and blur events from CEM output#11386
Merged
Conversation
These native events are picked up by CEM without @fires annotations and are not part of the component public API. Filter them out alongside the existing eventName false positive. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
sissbruecker
approved these changes
Mar 23, 2026
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
2 participants
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.
Summary
focusandblurnative events from CEM output by adding them to theignoredEventsdeny listdispatchEventcalls without@firesannotations and are not part of the component public APITest plan
yarn release:cemand verify no errorsfocusorblurevents remain in anycustom-elements.jsonfile🤖 Generated with Claude Code