Use design tokens for notification badge colors#136
Open
vku2018 wants to merge 1 commit into
Open
Conversation
|
@finiteskills is attempting to deploy a commit to the victorjames408gmailcom's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
--dash-dangerand--dash-on-dangertoken pairThis finishes the token-system acceptance item for the notification bell implementation currently on
main.Closes #58.
Validation
git diff --checkpassesapps/frontend/node_modules/.bin/tsc.CMD --noEmitruns, but the repo currently fails on pre-existing unrelated errors:app/dashboard/creator/campaigns/[id]/page.tsx: missing@/components/dashboard/creator/dashboard-headerapp/dashboard/creator/campaigns/page.tsx:CampaignListRowreceives unsupportedonClicknext lintis not available as a Next 16 subcommand in this repo; direct ESLint currently fails during config loading with an existing circular config serialization error before reaching changed files