Conversation
Adds ColorPairingTool to docs site, color-pairing utilities and components to vite-app, cds-finder app, guidelines documentation, and various supporting updates. Made-with: Cursor
…heming - Remove Color matching / Color pairs tab strip; single-flow layout - Scope LineChart scrubber overlay/line CSS vars to chart card for light playground - Hue-aware primitive matching and related adjustments Made-with: Cursor
🟡 Heimdall Review Status
🟡
|
| Code Owner | Status | Calculation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ui-systems-eng-team |
🟡
0/1
|
Denominator calculation
|
.cursor/rules/cds.mdc
Outdated
| @@ -0,0 +1,44 @@ | |||
| --- | |||
.cursor/mcp.json
Outdated
| "Figma": { | ||
| "url": "https://mcp.figma.com/mcp", | ||
| "headers": {} | ||
| }, |
apps/cds-finder/server/index.ts
Outdated
| @@ -0,0 +1,59 @@ | |||
| import cors from 'cors'; | |||
There was a problem hiding this comment.
This feature shouldn't require an application. Especially not an express server which we would have to set up infra for. The scope of changes for this feature should, in theory, be limited solely to apps/docs
| @@ -0,0 +1,20 @@ | |||
| --- | |||
| id: color-pairing-tool | |||
There was a problem hiding this comment.
let's discuss a different place to organize the color picker. Getting Started doesn't fool like the right place
| @@ -0,0 +1,188 @@ | |||
| /* ── Color Picker ──────────────────────────────────────────────────── */ | |||
There was a problem hiding this comment.
i dont think changes were meant to be made to vite-app. Likely the agent wen through multiple implementation attempts and forgot to clean up the changes made here. All the changes under vite-app should be removed
package.json
Outdated
| @@ -202,6 +193,7 @@ | |||
| "postcss-sort-media-queries": "^4.2.1", | |||
| "postcss-styled-syntax": "^0.7.1", | |||
| "prettier": "^3.6.2", | |||
| "puppeteer": "^24.37.5", | |||
guidelines/Untitled
Outdated
| @@ -0,0 +1 @@ | |||
| https://www.nerdwallet.com/banking/best/high-yield-online-savings-accounts | |||
| @@ -260,20 +260,19 @@ export async function docgenRunner(params: DocgenRunnerParams): Promise<PluginCo | |||
| template: 'shared/objectMap', | |||
| }); | |||
|
|
|||
| /** Styles API data - extracted from *ClassNames exports */ | |||
There was a problem hiding this comment.
im skeptical these docgen changes impact anything - we should remove all the changes under that folder
guidelines/overview-setup.md
Outdated
| @@ -0,0 +1,125 @@ | |||
| # Setup Guide | |||
15d5c80 to
1f1f05e
Compare
hcopp
left a comment
There was a problem hiding this comment.
Love the idea! Hopefully this can help you talk with Cursor about how to clean things up.
Also if you could get sample screenshots, description of your intended changes, and a link to the figma in the PR description that would be very helpful!
| @@ -74,9 +54,6 @@ export const MetadataLinks = memo(({ source, storybook, changelog, figma }: Meta | |||
| </LinkChip> | |||
| </Tooltip> | |||
| )} | |||
| <Chip compact onClick={handleCopyLLMDoc} start={<Icon color="fg" name="copy" size="s" />}> | |||
| Copy for LLM | |||
| </Chip> | |||
There was a problem hiding this comment.
nit: these are normally svg, can we do that?
| import { Icon } from '@coinbase/cds-web/icons'; | ||
| import { TextInput } from '@coinbase/cds-web/controls'; | ||
| import { toHex, hsbToRgb, rgbToHsb, parseColorInput } from './colorUtils'; | ||
| import styles from './ColorPicker.module.css'; |
There was a problem hiding this comment.
Can you run yarn nx run docs:lint --fix
| </Box> | ||
| <LineChart | ||
| enableScrubbing | ||
| height={{ base: 110 }} |
There was a problem hiding this comment.
You can just do height={110}
| alt="" | ||
| src={imgSrc || '/img/checker-placeholder.png'} | ||
| style={{ width: '100%', height: '100%', objectFit: 'cover' }} | ||
| /> |
There was a problem hiding this comment.
Do we need this checker placeholder png? Maybe we could make it a simple svg
| width: '100%', | ||
| height: '100%', | ||
| flexGrow: 1, | ||
| }} |
There was a problem hiding this comment.
Can we set these on Box instead of in styles props
| padding: '1px 5px', | ||
| borderRadius: 3, | ||
| whiteSpace: 'nowrap', | ||
| }; |
There was a problem hiding this comment.
Ideally we don't need custom CSS here, but if anything we should be consistent with a separate module.css file as we have elsewhere. We can do <Text background={X} borderRadius={100} ... /> instead.
| CDS layout components use inline styles generated from their style props, | ||
| which have higher specificity than CSS class rules. !important is required | ||
| here to override those inline styles at mobile breakpoints. | ||
| ────────────────────────────────────────────────────────────────────────── */ |
There was a problem hiding this comment.
We shouldn't need to use style props, but instead use our regular component props which support responsive values.
| @@ -0,0 +1,3 @@ | |||
| import type React from 'react'; | |||
|
|
|||
| export const monoStyle: React.CSSProperties = { fontFamily: 'CoinbaseMono, monospace' }; | |||
There was a problem hiding this comment.
Is this needed? We normally don't use mono font and even then don't have Coinbase fonts in our docs
| default: | ||
| return state; | ||
| } | ||
| } |
There was a problem hiding this comment.
We normally don't use a state file, but I get it could be funky here. Ideally we have a parent component which holds the state, and then passes the state components as props to different children based on what step we are on.
What changed? Why?
Root cause (required for bugfixes)
UI changes
Testing
How has it been tested?
Testing instructions
Illustrations/Icons Checklist
Required if this PR changes files under
packages/illustrations/**orpackages/icons/**Change management
type=routine
risk=low
impact=sev5
automerge=false