Migrate host code onto the consolidated @spudly/ui surface (pages/views; no widget or icon imports) — completes the #413 adoption
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start with the disposition table in spudly/design-system#438 and audit this repo’s @spudly/ui imports across the 64 page files and 102 widget-import files. Apply the listed page/view replacements, icon-name data, and isLoading to loading renames; check docs/manual-tests.md for the signed-out preview and footer verification. Done means the audit shows only allowed specifiers and CI and the scoped manual checks pass; the issue requires an approved plan and is blocked on #438.
Written by the indexing model from the issue text.
Description
Summary
Host-side migration onto the consolidated @spudly/ui surface delivered by spudly/design-system#438. This issue executes the remaining adoption scope of #413 once the DS coverage release lands — no back-and-forth: design-system#438's plan (Part 0) dispositions every @spudly/ui specifier in this repo before its PR opens.
Blocked by: spudly/design-system#438 (carries blocker; this issue carries blocked).
End state for this repo
- Imports from
@spudly/uiuse only: pages,eciperayTheme,tokens(incl. tag colors),createTamaguiConfig. @spudly/ui/pagesspecifiers move to the root (45 page names, 64 files — specifier change only).- Zero widget imports (~30 distinct today across 102 files: Text, Button, RatingForm, SectionCard, ScreenContainer, Alert, TextLink, Card, TextAction, the form fields, Dialog, Badge, Spinner, etc.). Each host-composed fragment is replaced by the DS page/view expression named in design-system#438's disposition table.
- Zero icon imports: the
@spudly/ui/iconssubpath usage (2 files, 10 icons) is replaced by icon names passed as data to pages/frames. - DS-prop rename:
isLoading→loading(15 files). PublicPageFramereceives thefooterdata (incl. the Do Not Sell link) — this is the #425 fix path; when this migration lands and QA verifies the signed-out footer on the preview, #425 closes and the hold on release PR #423 clears.
Acceptance
- The disposition-table audit from design-system#438, re-run against this repo on the new DS release, returns only allowed specifiers.
- CI green; manual preview test pass per
docs/manual-tests.mdtrigger scoping (signed-out/read-only sections; the footer verification for #425 included).
Notes
- Plan gate applies: an implementation plan will be posted on this issue for Stephen's approval before work starts (expected to be a short plan referencing design-system#438's disposition table).
- #413 stays open as the adoption tracker and closes when this issue's PR merges.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8h 56m
- Merged PRs (30d)
- 200
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from spudly/eciperay
-
blocker bug in_progress priority-p1 qa
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
spudly/eciperay#425 · 4 comments ·
Maintainers usually reply within 1 day
-
blocked needs_human priority-p2
Difficulty 2/5 Half a day Newbie friendliness 68/100
spudly/eciperay#31 · 1 comment ·
Maintainers usually reply within 1 day
-
chore(deps): upgrade @anthropic-ai/sdk 0.134.0 -> 1.x with API-migration verificationPossibly taken @spudly claimed this today. Openenhancement priority-p2
Difficulty 4/5 3-5 days Newbie friendliness 20/100
spudly/eciperay#447 · 4 comments ·
Maintainers usually reply within 1 day
-
enhancement in_progress priority-p2
Difficulty 4/5 3-5 days Newbie friendliness 48/100
spudly/eciperay#419 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement in_progress priority-p2
Difficulty 4/5 3-5 days Newbie friendliness 55/100
spudly/eciperay#417 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
LibreChat-AI/LibreChat#17875 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
category:helper tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
LanternOps/breeze#11285 ·
Maintainers usually reply within 1 day
-
area: core area: docs good first issue help wanted lane: free-agent priority: P3 roadmap size: XS type: task
Difficulty 1/5 Under an hour Newbie friendliness 86/100
arminazimi/seaworthy#701 ·
Maintainers usually reply within 1 day