chore: correct generation of events in cem #10827
Merged
Conversation
This file contains 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.
TypeScript decorators can be imported in two ways:
@ui5/webcomponents-base/dist/decorators/{decoratorName}.js@ui5/webcomponents-base/dist/decorators.jsRecently, the
event.jsdecorator was deprecated and replaced withevent-strict.js. When using the default import, the decorator could retain its old name, and the custom element analyzer would still process it correctly. However, when using the named import, the@eventStrictdecorator was not processed, leading to missing parts of the component's API.This PR adjusts the custom element analyzer to correctly process both
@eventand@eventStrictdecorators.