fix: Detect deprecations in new expressions with ID #437
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
RandomByte
requested changes
Dec 4, 2024
This solves the gap of not detecting usage of deprecated UI5 metadata (e.g. properties, aggregations, events) when using the constructor with an ID as first argument.
matz3
force-pushed
the
fix-detect-deprecated-property
branch
from
38707c1 to
f804d6f
Compare
RandomByte
approved these changes
Dec 4, 2024
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.
This solves the gap of not detecting usage of deprecated UI5 metadata
(e.g. properties, aggregations, events) when using the constructor
with an ID as first argument.