Skip to content

fix(component-library-styles): map legacy brand light washes to CADS … - #74128

Merged
moshebaricdo merged 1 commit into
stagingfrom
fix/cads-alias-brand-light-washes
Jul 27, 2026
Merged

fix(component-library-styles): map legacy brand light washes to CADS …#74128
moshebaricdo merged 1 commit into
stagingfrom
fix/cads-alias-brand-light-washes

Conversation

@moshebaricdo

Copy link
Copy Markdown
Contributor

Summary

  • Under codeai-next, certain light values were aliasing to new mid values, which are too dark for use in the contexts where it was being applied. All have been updated to alias to new light values. This addresses issues observed during the bug bash with dark alerts making text difficult to read, and also addresses excessively dark text brand color button hover states.
  • Note: CADS mid values are net-new, marketing-aligned, darker steps; no components currently use these values.

Screenshots:

Before After
Screenshot 2026-07-27 at 1 02 42 PM Screenshot 2026-07-27 at 1 02 59 PM
Before After
Screenshot 2026-07-27 at 1 03 40 PM Screenshot 2026-07-27 at 1 03 48 PM

|

Links

  • Jira:

Testing story

Deployment notes

Privacy and security

…light

Legacy background-*-light and purple-hover were aliased to CADS mid, which
is a net-new darker step. Map them to light so unmigrated call sites keep
the wash fill.

Co-authored-by: Cursor <cursoragent@cursor.com>
@moshebaricdo
moshebaricdo requested a review from a team as a code owner July 27, 2026 17:15
@github-actions

Copy link
Copy Markdown

🖼️ Storybook Visual Comparison Report

✅ No Storybook eyes differences detected!

@moshebaricdo
moshebaricdo merged commit 8226937 into staging Jul 27, 2026
18 checks passed
@moshebaricdo
moshebaricdo deleted the fix/cads-alias-brand-light-washes branch July 27, 2026 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants