feat(kumo): surface LinkButton and RefreshButton in registry, CLI, docs, Figma#466
Draft
ascorbic wants to merge 1 commit intocloudflare:mainfrom
Draft
feat(kumo): surface LinkButton and RefreshButton in registry, CLI, docs, Figma#466ascorbic wants to merge 1 commit intocloudflare:mainfrom
ascorbic wants to merge 1 commit intocloudflare:mainfrom
Conversation
…cs, Figma Adds a KUMO_REGISTRY_COMPONENTS marker on a component directory's index.ts to register multiple sibling components from a single source file. The registry codegen previously assumed one component per directory, which silently dropped LinkButton and RefreshButton (both co-located in button/button.tsx). They now have their own registry entries, doc pages, sidebar nav entries, and Figma generator data without sharing Button's attribution. - Registry: discovery emits one ComponentConfig per registered component name. Variant tables are looked up by KUMO_<NAME>_VARIANTS, with alias chains resolved so KUMO_LINK_BUTTON_VARIANTS = KUMO_BUTTON_VARIANTS works. - CLI: kumo doc/ls now find LinkButton and RefreshButton. - Docs: new pages at /components/link-button and /components/refresh-button. Sidebar nav and button.mdx narrative point at the new pages. - Demos: LinkButton and RefreshButton demos extracted into their own files to feed the registry generator's per-component bucketing. - Figma: link-button and refresh-button generators read their own registry entries instead of borrowing from Button. - Lint: enforce-variant-standard now permits KUMO_<NAME>_VARIANTS exports for any PascalCase component declared in the same file.
3e084ae to
b571705
Compare
commit: |
Author
|
/review |
Contributor
Docs PreviewCommit: |
Contributor
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.





















Adds a
KUMO_REGISTRY_COMPONENTSmarker on a component directory's index.ts to register multiple sibling components from a single source file. The registry codegen previously assumed one component per directory, which silently droppedLinkButtonandRefreshButton(both co-located in button/button.tsx). They now have their own registry entries, doc pages, sidebar nav entries, and Figma generator data without sharing Button's attribution.ComponentConfigper registered component name. Variant tables are looked up byKUMO_<NAME>_VARIANTS, with alias chains resolved soKUMO_LINK_BUTTON_VARIANTS = KUMO_BUTTON_VARIANTSworks.LinkButtonandRefreshButton./components/link-buttonand/components/refresh-button. Sidebar nav andbutton.mdxnarrative point at the new pages.LinkButtonandRefreshButtondemos extracted into their own files to feed the registry generator's per-component bucketing.Button.KUMO_<NAME>_VARIANTSexports for any PascalCase component declared in the same file.