Conversation
…tory Reorganize 164 Blade components from 23+ scattered _components directories into a unified apps/blade/src/app/_components/ structure with logical subdirectories mirroring route organization: - navigation/ - Session navbar, user dropdown, logo, QR code components - admin/charts/ - All demographic chart components - admin/club/ - Club check-in, data, events, members subdirectories - admin/hackathon/ - Hackathon management (check-in, data, events, hackers, rooms, judge, control-room, judge-assignment, roomAssignment) - admin/forms/ - Form editor and response viewer components - admin/roles/ - Role configuration components - admin/banquet-raffle/ - Raffle draw component - dashboard/ - Dashboard components (hacker, hackathon, member subdirectories) - forms/ - Public form components with _hooks subdirectory - judge/ - Judge interface components - settings/ - Profile and settings components - shared/ - Cross-cutting utilities (scanner, csv-importer, SortButton, etc.) Updated 78+ import statements across 49 files to use ~/app/_components/ pattern for consistency. Removed old src/components/ directory and all empty route-specific _components directories. Added @types/canvas-confetti to resolve TypeScript compilation errors.
…s directory Move components from 3 scattered route-specific _components directories into the unified apps/club/src/app/_components/ structure: - contact/_components/ (4 files + assets) → _components/contact/ - links/_components/ (2 files + assets) → _components/links/ - officers/_components/ (2 files + assets) → _components/officers/ Updated import paths in contact/page.tsx, links/page.tsx, and officers/page.tsx to use ~/app/_components/ pattern for consistency. Removed all empty route-specific _components directories. Total: 67 component files now consolidated in apps/club/src/app/_components/ organized by feature area (contact, landing, links, navigation, officers).
- Move hooks from _components/hooks/ to dedicated src/hooks/ directory in 2025 app - Update 7 component imports to use ~/hooks/ pattern - Remove duplicate UI components from gemiknights (accordion, card, separator) - Update gemiknights components to import from @forge/ui instead
|
Important Review skippedToo many files! This PR contains 260 files, which is 110 over the limit of 150. You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
Spyderma9
added
Documentation
Resolve conflicts from component consolidation: - Moved new files (HowFound, RatingRanking, view-feedback-button, view-rating-button, connection-handler) to consolidated _components directory - Updated import paths in form-responder-client.tsx to use consolidated structure - Updated import paths in forms/[formName]/page.tsx to reference consolidated components
…mponents structure
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
1 participant
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.
Why
The codebase was messy
What
Issue(s): #338
Organized components that were scattered all around the codebase into single src/app folders that contain everything for that app
Test Plan
Ran apps to make sure I didn't break anything
Checklist
db:pushbefore merging