-
Notifications
You must be signed in to change notification settings - Fork 78
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
Calendar event colors should accept color keywords #5743
Comments
Whats the array situation look like i.e. what do you have to do thats not ideal? But we are assuming you use on color pallette colors in the customization to stick to the "brand" https://github.com/infor-design/enterprise/blob/main/app/views/components/calndar/test-event-color-override.html#L55-L56 |
Hi Tim, Current workaround is to maintain a map of all color keywords and their hex values (ie this list https://www.w3.org/wiki/CSS/Properties/color/keywords). Regarding the color palette, our customers have custom colors already set up for certain events (eg vacation/PTO/sick day) and they need to be consistent across the app. That might mean some inconsistency in branding but it's required for some use cases. |
The colors on the event types displayed in the calendar is also reflected in the legend. However, if you create a new event it will not match the legend color of event.
|
BDD attached |
@tjamesallen15 where are we on this? |
this is now working as expected. v4.60.0-beta1 . thank you |
Is your feature request related to a problem? Please describe.
Calendar events currently only accept a hex value color (eg "#00FF00") when overriding the color of an event. Currently we get custom colors for calendar events both by hex and by keyword (eg "papayawhip").
Describe the solution you'd like
Calendar event should accept color keywords as well, instead of just accepting hex values.
Describe alternatives you've considered
WFM is having to maintain an array of color keywords and convert them to hexes, but this is not ideal.
The text was updated successfully, but these errors were encountered: