Skip to content

Add packages/pretui with the Pret UI pilot components - #6208

Open
richardhjtan wants to merge 3 commits into
mainfrom
cs-13047-packages-pretui
Open

richardhjtan wants to merge 3 commits into
mainfrom
cs-13047-packages-pretui

Conversation

@richardhjtan

@richardhjtan richardhjtan commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Adds packages/pretui, a directory that is both a pnpm workspace package and a realm, holding the first batch of Pret UI components: Button, IconButton, Switch, Checkbox and the shared pretui-primitives module, each with its write-up.

Both consumers resolve one spelling, @cardstack/pretui/components/button. The host takes it as a workspace dependency: package.json#exports maps every subpath to its .gts source, so Vite compiles imported components into the bundle per file and nothing else ships. Cards take it through the realm the realm-server serves from this same directory, so the index tracks the dependency and importers reindex when a component changes. There is no build step, no dist and no externals shim.

The package follows boxel-ui's dev shape (v2 addon metadata, addon-main shim) and experiments-realm's realm shape (realm.json, index.json, *.test.gts alongside the source). Spec cards live in the catalog realm only, so none are here. Usage and example pages are not in this batch; they depend on the kit-wide freestyle scaffolding and move with it.

Host consumption, realm-server wiring, the experiments-realm proof card, catalog Specs and the touch-gated CI job follow in their own PRs.

Verified: pnpm lint in packages/pretui (ember-template-lint + ember-tsc, test file included) passes, and pnpm install --frozen-lockfile succeeds.

🤖 Generated with Claude Code

Pret UI is consumed from one monorepo directory by two consumers through
one import spelling, `@cardstack/pretui/components/button`: the host as a
pnpm workspace dependency whose package.json#exports maps every subpath
to its .gts source, and cards through the realm the realm-server serves
from the same directory.

This first batch carries Button, IconButton, Switch, Checkbox and the
shared pretui-primitives module, with each component's write-up and Spec
instance. The usage and example pages depend on the kit-wide freestyle
scaffolding and move with it in a later batch.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Host Test Results

    1 files  ±0      1 suites  ±0   2h 10m 20s ⏱️ + 3m 31s
4 914 tests ±0  4 900 ✅ ±0  14 💤 ±0  0 ❌ ±0 
4 929 runs  ±0  4 915 ✅ ±0  14 💤 ±0  0 ❌ ±0 

Results for commit 881715c. ± Comparison against earlier commit f1d467a.

Realm Server Test Results

    1 files  ±0    244 suites  ±0   1h 20m 11s ⏱️ - 4m 26s
3 618 tests ±0  3 618 ✅ ±0  0 💤 ±0  0 ❌ ±0 
3 669 runs  ±0  3 669 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 881715c. ± Comparison against earlier commit f1d467a.

richardhjtan and others added 2 commits September 20, 2026 23:54
Spec cards for Pret UI components live in the catalog realm only, so the
package carries none. The component headers and inline notes now state the
current contract without the kit-wide context they were written in.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Comments and test names in packages/pretui state what an alias does for the
component's own contract rather than which library's vocabulary it mirrors.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@richardhjtan
richardhjtan marked this pull request as ready for review September 21, 2026 05:48
@richardhjtan
richardhjtan requested review from a team and lukemelia September 21, 2026 05:48
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-09-21T05:49:01.734373Z 881715c Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant