svelte-kit-vice

Commit Graph

Author	SHA1	Message	Date
dev	72ff90b71f	docs: consolidate kind contract + composition norms (sweep) After several commits on pickers, the docs lagged behind the actual contract. This sweep aligns PENDIENTES + eidos README + DEMO_AUTHORING_GUIDE with what landed. PENDIENTES.md: - 'Pickers' section rewritten as a consolidated state table. Everything done is marked hecho; the two big items (MonthPicker/YearPicker, MonthRangePicker/YearRangePicker as separate components) are explicitly descartar because they're achieved via <DatePicker kind='X'> / <DateRangePicker kind='X'>. Duplicating component surfaces for what a prop captures is doctrinally rejected. - Promotion of YearView/MonthView to standalone <YearCalendar> / <MonthCalendar> is diferir — currently coupled to picker provider context, no real use case outside picker yet. - Time picker / color picker propagation of modal+Footer pattern marked implementar. - Playwright browser tests for the picker flows marked implementar — range state machine + kind chip + modal need coverage. - Range view: 'differentiate start/end vs in-range visually' added to theming backlog (currently all 3 use primary-solid, range tint not visible). - Two new norms N-6 and N-7: * N-6 picker kind = single source for input + view. Filtering lives at DateFieldProvider (soma), consumers iterate the segments output. Views are canonical Eidos parts. * N-7 composition over visibility props. Parts opt-in by inclusion, not by boolean prop. Demo wraps parts in {#if showX} with local state so the UI toggles still work without leaking demo logic into the parts. eidos/README.md: - New 'Cambios 2026-05-21 — pickers: kind + composition' section summarising kind + Footer composition + provider helpers + the 'composition wins, no separate variant components' decision. DEMO_AUTHORING_GUIDE.md: - §12.9 'Composition over visibility props': right vs wrong example for <DatePicker.Footer> with the Clear/Cancel/Close children. - §12.10 'Chakra-style kind for picker variants': demo skeleton for the Input snippet (no filter) and the Content {#if} branch. Task list: #29 retired (MonthRangePicker/YearRangePicker as separate components — replaced by <DateRangePicker kind='X'>). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	5 months ago

Author

SHA1

Message

Date

dev

72ff90b71f

docs: consolidate kind contract + composition norms (sweep)

After several commits on pickers, the docs lagged behind the actual
contract. This sweep aligns PENDIENTES + eidos README +
DEMO_AUTHORING_GUIDE with what landed.

PENDIENTES.md:
- 'Pickers' section rewritten as a consolidated state table.
  Everything done is marked hecho; the two big items
  (MonthPicker/YearPicker, MonthRangePicker/YearRangePicker as
  separate components) are explicitly **descartar** because they're
  achieved via <DatePicker kind='X'> / <DateRangePicker kind='X'>.
  Duplicating component surfaces for what a prop captures is
  doctrinally rejected.
- Promotion of YearView/MonthView to standalone <YearCalendar> /
  <MonthCalendar> is **diferir** — currently coupled to picker
  provider context, no real use case outside picker yet.
- Time picker / color picker propagation of modal+Footer pattern
  marked **implementar**.
- Playwright browser tests for the picker flows marked
  **implementar** — range state machine + kind chip + modal need
  coverage.
- Range view: 'differentiate start/end vs in-range visually' added
  to theming backlog (currently all 3 use primary-solid, range
  tint not visible).
- Two new norms N-6 and N-7:
  * N-6 picker kind = single source for input + view. Filtering
    lives at DateFieldProvider (soma), consumers iterate the
    segments output. Views are canonical Eidos parts.
  * N-7 composition over visibility props. Parts opt-in by inclusion,
    not by boolean prop. Demo wraps parts in {#if showX} with local
    state so the UI toggles still work without leaking demo logic
    into the parts.

eidos/README.md:
- New 'Cambios 2026-05-21 — pickers: kind + composition' section
  summarising kind + Footer composition + provider helpers + the
  'composition wins, no separate variant components' decision.

DEMO_AUTHORING_GUIDE.md:
- §12.9 'Composition over visibility props': right vs wrong example
  for <DatePicker.Footer> with the Clear/Cancel/Close children.
- §12.10 'Chakra-style kind for picker variants': demo skeleton
  for the Input snippet (no filter) and the Content {#if} branch.

Task list: #29 retired (MonthRangePicker/YearRangePicker as separate
components — replaced by <DateRangePicker kind='X'>).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

1 Commits (0e0fbc05d727ce9aedeb5a629e733b3f5a79911d)