Skip to content

refactor(structure): consolidate components into app/components - #732

Merged
Calebux merged 1 commit into
zintarh:mainfrom
Vox-d-glitch:fix/588-single-component-tree
Oct 1, 2026
Merged

Calebux merged 1 commit into
zintarh:mainfrom
Vox-d-glitch:fix/588-single-component-tree

Conversation

@Vox-d-glitch

Copy link
Copy Markdown
Contributor

I moved every component from the top-level components/ and src/components/ trees into app/components/ in one change, following the App Router convention of keeping app code under app/, and updated the imports. src/components/TransactionsOfFury.tsx, the virtualized variant, would have collided with the existing app/components/TransactionsOfFury.tsx, so it is now VirtualizedTransactionsOfFury.tsx. The ErrorCard story now imports from @storybook/nextjs like the other stories, since it is now inside Storybook's app/** story glob.

No tsconfig.json alias pointed at the retired trees, so the @/*, @app/* and @src/* aliases stay as they are and the moved imports use the existing @/app/components/... and relative paths. CONTRIBUTING.md now explains where components live and why, and points the contact-list docs at app/components/. A new ESLint rule fails on any file added under components/ or src/components/, so the fragmentation can't come back.

Closes #588

Move every component from the top-level components/ and src/components/
trees into app/components and update their imports. The virtualized
src/components/TransactionsOfFury.tsx becomes
VirtualizedTransactionsOfFury.tsx so it does not collide with the
existing app/components/TransactionsOfFury.tsx, and the ErrorCard story
now uses @storybook/nextjs like the other stories.

Document the single component location in CONTRIBUTING.md and add an
ESLint rule that fails on any file added to the retired trees.
@drips-wave

drips-wave Bot commented Sep 28, 2026

Copy link
Copy Markdown

@Vox-d-glitch Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@vercel

vercel Bot commented Sep 28, 2026

Copy link
Copy Markdown

@Vox-d-glitch is attempting to deploy a commit to the zintarh Team on Vercel.

A member of the Team first needs to authorize it.

@Calebux
Calebux merged commit c0908a1 into zintarh:main Oct 1, 2026
1 check failed
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.

refactor(structure): three component trees — app/components, src/components, and components/

2 participants