[codex] Remove duplicate warning colour token - #147
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
FleetAdmiralJakob
force-pushed
the
codex/remove-warning-colour
branch
from
June 26, 2026 18:12
adf02ed to
e1e6349
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
warning/warningSubtlecolour tokens from the design-system constants, Tailwind palette, and global CSS variables.WarningBannercomponent to use the existinginfocolour token for advisory banner styling.PlanningHintBanner/shared-banner system from PR Extract reusable warning banner and link planning hints #140 intact, so learning-plan hints and notification guidance now pick up the semantic colour change from one place.#FF9500is documented only as thewrongstatus colour.Why
The
warningtoken duplicated thewrongcolour values, which made the design system carry two names for the same visual role. After PR #140 introduced a reusable warning banner system, the right integration point is the shared banner component rather than the individual screens.Impact
wrong.infocolour instead of the orangewrongduplicate.warningclasses, so new UI should choose the more specificinfo,wrong, ordestructivetoken.release-v-1.0.3branch so it works with the reusable warning-link changes from PR Extract reusable warning banner and link planning hints #140.Validation
env PATH="/Users/jakobroessner/.local/share/fnm/node-versions/v22.23.1/installation/bin:$PATH" node_modules/.bin/tsc --noEmitenv PATH="/Users/jakobroessner/.local/share/fnm/node-versions/v22.23.1/installation/bin:$PATH" node_modules/.bin/biome lint .env PATH="/Users/jakobroessner/.local/share/fnm/node-versions/v22.23.1/installation/bin:$PATH" node_modules/.bin/eslint src convex index.tsNote:
pnpm typecheckcould not run through the current shell because the active global runtime is Node 24 with pnpm 11, while the repo expects Node >=22 <24 and pnpm 10. The checks above were run directly against the installed repo dependencies using local Node 22.23.1.Base branch
This PR targets
release-v-1.0.3because the cleanup belongs on the release branch where the design-system and reusable warning-banner work has landed.