-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: Detect usage of non exported values by library.js #468
Conversation
Hi @KlattG , Would you take a look at the new messages in here, please? |
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.
LGTM
0e40a22
to
8bb9d55
Compare
Hi @KlattG , Would you take a look again, please? Here's an example produced message: Cheers |
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.
LGTM
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.
LGTM
"sap/ui/core/library", | ||
// This ones are correct- elements, imported as modules | ||
"sap/ui/unified/DateTypeRange", | ||
"sap/ui/unified/CalendarDayType", |
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.
This is actually a pseudo module (see finding in test snapshot), and it should rather be accessed via the library module.
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.
Yep, and that's why I added it. With the prevous miss, actually the pseudo modules were also reported as non exported values. Let's leave this as a safeguard.
JIRA: CPOUI5FOUNDATION-957