Add interactive wedding seating planner with drag-and-drop hall layout#1
Open
mbil4l wants to merge 1 commit into
Open
Add interactive wedding seating planner with drag-and-drop hall layout#1mbil4l wants to merge 1 commit into
mbil4l wants to merge 1 commit into
Conversation
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
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.
Motivation
Description
src/app/page.tsxwith a React/TypeScript seating planner that definesGuestandTabletypes and seedsINITIAL_GUESTSandINITIAL_TABLES.assignGuestand per-tableonDrophandlers, and expose an+ Add Tableaction viaaddTableto expand layout dynamically.GuestChip,Zone, andStatCardand aPARTY_COLORSmap for per-party styling.Stage,Dance Floor,Photo Booth,Buffet), circular table components showing occupancy, and an unassigned waiting area.Testing
npm run build(callsnext build), which completed successfully and generated static pages (Compiled successfullyand prerendered pages) ✅.npm run lintbut the environment triggered Next.js' interactive ESLint setup prompt, so linting could not be completed non-interactively in this runCodex Task