You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
근거: eslint-agent/probe_static.tsx: css() cannot use U at build time
수정 방향: align lint/docs with extractor or narrow claim
FN-03 (P1, MISMATCH) Feature docs spread a class-name string as component props
근거: apps/landing/src/app/(detail)/docs/features/page.mdx:227-234 shows const cardStyles = css(...) followed by <Box {...cardStyles} />; the API page says css returns a string at docs/api/css/page.mdx:11, and the probe returns a string
수정 방향: change the feature example to <Box className={cardStyles} styleOrder={...}> (or a style-object example if spreading was intended)
CSS-09 (P2, MISMATCH) Published responsive breakpoint table disagrees with emitted defaults
근거: cascade.tsx emits slot 3 at min-width:992px and slot 5 at 1600px; typography docs list 1024px and 1640px (apps/landing/src/app/(detail)/docs/devup/typography/page.mdx:178-185). Other observed defaults are 480/768/1280 as documented.
수정 방향: Decide which sequence is canonical, then update either default constants or all public breakpoint docs/examples and lock the table with a docs-facing test.
CSS-10 (P2, MISMATCH) Two-theme color output has no fallback for pre-Baseline-2024 browsers
근거: Shared two-theme colors emit only --primary:light-dark(#F00,#00F). There is no preceding plain fallback or per-theme override. MDN marks light-dark() Baseline 2024 / available across latest browsers since May 2024, and notes older browsers may not support it. Current Chromium accepts it.
수정 방향: Publish an explicit browser-support floor. If older browsers are supported, emit a plain default variable first and a guarded light-dark() override, or always use per-data-theme variables.
FN-10 (P2, MISMATCH) styled(makeStyles()) behavior contradicts its explicit documentation
근거: styled.div(makeStyles()) compiles to a red class in styled-dynamic.tsx; docs say “A whole style object computed that way (css(makeStyles()), styled.div(makeStyles())) is a build error” at docs/features/page.mdx:238
수정 방향: decide the contract, then either reject whole computed objects consistently or update docs and add exact/uncertain function-result tests
JSX-11 (P2, MISMATCH) Selector documentation is materially narrower than the public type surface
근거: types generate group forms for every simple/advanced selector and support direct @media .../@supports .../@container ... plus record forms (packages/react/src/types/props/selector/index.ts:34-58,91-107); docs list only four group selectors and headline only underscore at-rules (apps/landing/src/app/(detail)/docs/api/group-selector/page.mdx:43-84, api/selector/page.md…
수정 방향: generate selector reference tables from the type/source unions and document advanced params, generated group keys, pseudo-elements, styleOrder, and every at-rule spelling.
선택 (16)
DOC-05 (P2, MISMATCH) N/M-base alphabet/count documentation is wrong
근거: num_to_nm_base.rs has a-z plus _ as 27 single-character names and digits in continuation
수정 방향: document exact alphabets/order and 27 count
DOC-07 (P2, MISMATCH) Generated declaration path is presented as fixed
근거: plugin source joins configurable distDir with theme.d.ts
수정 방향: state default and configurable path
DOC-08 (P2, MISMATCH) Figma documentation links two different plugin IDs
근거: legacy ID 1412341601954480694 vs current ID 1446848873498976065
수정 방향: verify live listing and consolidate
DOC-12 (P2, PERF) “Latest” benchmarks/version are stale
근거: docs say 1.0.40/former lite evaluator; probe banner is 1.0.81/current Boa
수정 방향: label historical or rerun
DOC-15 (P2, MISMATCH) Components README documents the wrong package
문서가 실제 동작과 다르거나 빠진 부분입니다. README의 "Complete CSS-in-JS Syntax Coverage" 같은 과장된 문구는 이번에 한계를 반영해 고칩니다.
전체 계획과 결정 사항은 추적 이슈(#682)에 있습니다. 조사 기준 커밋:
77daad74(현재 maind0b84255).결정에 따른 작업
styled()확장). 마이그레이션 문서에도 안내light-dark(),@layer,:is())style도 전달해야 함theme.breakpoints), Tailwind 이름과 같은 class의 변환 규칙, 지원 범위발견 항목
심각도: P0 = 흔한 사용에서 조용히 틀리거나 크래시, P1 = 흔한 패턴이 명시적 에러로 막히거나 드물게 조용히 틀림, P2 = 드문 경우·도구/문서 불일치, P3 = 있으면 좋음.
필수 (2)
권장 (15)
apps/landing/src/app/(detail)/docs/features/page.mdx:227-234showsconst cardStyles = css(...)followed by<Box {...cardStyles} />; the API page sayscssreturns a string atdocs/api/css/page.mdx:11, and the probe returns a string<Box className={cardStyles} styleOrder={...}>(or a style-object example if spreading was intended)cascade.tsxemits slot 3 atmin-width:992pxand slot 5 at1600px; typography docs list1024pxand1640px(apps/landing/src/app/(detail)/docs/devup/typography/page.mdx:178-185). Other observed defaults are 480/768/1280 as documented.--primary:light-dark(#F00,#00F). There is no preceding plain fallback or per-theme override. MDN markslight-dark()Baseline 2024 / available across latest browsers since May 2024, and notes older browsers may not support it. Current Chromium accepts it.light-dark()override, or always use per-data-themevariables.styled(makeStyles())behavior contradicts its explicit documentationstyled.div(makeStyles())compiles to a red class instyled-dynamic.tsx; docs say “A whole style object computed that way (css(makeStyles()),styled.div(makeStyles())) is a build error” atdocs/features/page.mdx:238@media .../@supports .../@container ...plus record forms (packages/react/src/types/props/selector/index.ts:34-58,91-107); docs list only four group selectors and headline only underscore at-rules (apps/landing/src/app/(detail)/docs/api/group-selector/page.mdx:43-84,api/selector/page.md…params, generated group keys, pseudo-elements,styleOrder, and every at-rule spelling.선택 (16)
_firstselector maps to nonstandard:firstin docs