-
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
feat: allow easy customizing of required indicator's color #2810
Conversation
@web-padawan Sorry, but I'm kinda lost how to create a test for this change.. the whole JS is a little bit to magical for me.. I looked for a test that checks that the other variable ( |
@knoobie Thanks for the PR. No worries, we can help with adding tests for this on Monday. |
I don't remember any more if we’ve discussed this previously, but I feel we could/should drop the opacity property from the indicator, and let it be shown for both non-filled and filled fields. |
Yes we discussed it: #85 but let's make sure we land that in a separate PR, it will require adding some visual tests. |
Updated PR and removed the opacity change |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
The PR looks good to me. I'm going to merge it as is, then we can think of adding visual tests to Lumo separately. |
This ticket/PR has been released with platform 22.0.0. |
Description
Allows easy customization of the default required indicator's color to allow for common use cases like red colored required indicator without overwriting the
part=required-indicator
for every component.Type of change
Checklist
Additional for
Feature
type of change--> Half / Half .. it was dicussed with Jouni in the ticket; but there is not AC created.