-
Notifications
You must be signed in to change notification settings - Fork 83
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
refactor: drop use of include option with registerStyles #2454
Conversation
96749a4
to
828b80d
Compare
828b80d
to
425b19a
Compare
packages/password-field/theme/lumo/vaadin-password-field-styles.js
Outdated
Show resolved
Hide resolved
} | ||
`; | ||
|
||
registerStyles('vaadin-combo-box-overlay', [overlay, menuOverlayCore, comboBoxOverlay], { |
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.
I was wondering if this PR addresses #1697 too? Or is that still an issue with new includes?
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.
Seems that this PR alone doesn't solve the issue. Maybe if we added some extra logic to registerStyles
to eliminate duplicate CSSResults etc
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
This ticket/PR has been released with platform 22.0.0.alpha3 and is also targeting the upcoming stable 22.0.0 version. |
Adds a deprecation warning for the
{ include }
option inregisterStyles
API.Also drops internal use of
{ include }
in favor of using ES modules for style sharing.It's really recommended to use the "Hide whitespace changes" option in the "Files changed" view of this PR.