[EuiBadge] : Handle invalid color entry

[akashgp09]

Signed-off-by: Akash Gupta [email protected]

Summary

This PR Fixes #3765
Handling invalid color entry passed to EuiBadge color prop

Checklist

• Check against all themes for compatibility in both light and dark modes
• Checked in mobile
• Checked in Chrome, Edge, and Firefox
  - [ ] Props have proper autodocs and playground toggles
• Added documentation
• Checked Code Sandbox works for the any docs examples
• Added or updated jest tests
• Checked for breaking changes and labeled appropriately
• Checked for accessibility including keyboard-only and screenreader modes
• A changelog entry exists and is marked appropriately

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[thompsongl]

jenkins test this

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4481/

[thompsongl]

jenkins test this

Error: Timed out waiting for: http-get://localhost:9999

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4481/

[thompsongl]

Hey @akashgp09

This looks great! It does, however, highlight the fact that our chromaValid function does not see rgba() strings as valid colors. You can see this in the snapshot change in this branch, where the test should've pass unchanged and without warning.
Previously, (apparently) the warning still occurred, but the color would still be used correctly.
We'll need to accept rgba() to avoid a breaking change.
If you want to attempt the change, great! If not, no problem; I can push a commit to this branch.

[akashgp09]

@thompsongl I have fixed it. Now it's accepting rgb string (as previously).
Let me know if anything missed out :‑P

[thompsongl]

LGTM! I think we will eventually want to update the validator util function(s) to accept strings withrgb(a) in the string, but this solves the more immediate problem.

I'm going to push one commit (I had it locally) to update the CL entry location. Will merge after CI passes.

[thompsongl]

jenkins test this

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4481/