Skip to content

Document per-entry file-path and export-shape conventions for fetched components #48

Description

@AnayDhawan

Fetched components land in at least 4 different, undocumented path conventions across the registries tested (src/components/ui/x.tsx, root-level PascalCase files, per-library subfolders), and export shape (named vs default, single vs multiple) varies per entry with nothing recording it.

Neither is predictable from components.json today; documenting the pattern per library would save every consumer from having to fetch first just to find out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationgood first issueGood for newcomers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions