-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Improve extraction of inline XML #547
base: main
Are you sure you want to change the base?
Conversation
The previous implementation extracted XML content from every options property, not just the actual XML definition/content. This lead to unnecessary empty inline JS files. Follow-up of #519
43d2ff6
to
6e42901
Compare
{ | ||
column: 17, | ||
line: 33, | ||
message: 'Call to deprecated function \'sapUiXmlView\'', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The deprecation is correct, but to me this seems a bit missleading. There's no such thing as sapUiXmlView
, but its assignment. While in the example, the solution is obvious, in real code this might not be the case and might lead to ambiguous situations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might try to enhance this in general by adding the original API name to the message. This is sometimes working, but I think in this case it does not, as the additionalMessage
is empty.
88a7fb3
to
df6c3ef
Compare
The previous implementation extracted XML content from every options
property, not just the actual XML definition/content.
This lead to unnecessary empty inline JS files.
Follow-up of #519