4 Commits (6a80607430574bcbc6fef2d838ffc21d939265e2)

Author	SHA1	Message	Date
Guillermo Pages	1b7497b6d2	fix(admin): duration validation + sport variation display ... Fixed two issues reported by user: 1. Slot definition duration validation error: - Changed step from "15" to "1" on duration input - HTML5 validation was failing because with min="1" and step="15", valid values were 1, 16, 31, 46, 61, 76, 91... (not 90!) - Now accepts any integer duration >= 1 minute - Error "nearest 76 or 91" resolved 2. Sport variation not showing in court edit form: - Updated Court type to include nested sport_variation structure - Backend now returns full sport_variation object with sport details - Updated CourtFormModal to extract sport_variation_id from nested structure: court.sport_variation.sport_variation_id - Added sport variation display in court list (e.g., "Padel - Indoor") - Maintains backward compatibility with deprecated flat field Changes: - SlotDefinitionForm: step="1" instead of step="15" - Court interface: added optional sport_variation nested object - ClubCourtsTab: reads sport_variation_id from nested structure - ClubCourtsTab: displays "Sport - Variation" in court list Related: Backend Brooke nested sport_variation response structure	1 month ago
Guillermo Pages	36c5fe2183	feat(admin): add sport variation selection to court creation + fix profile trim crash ... Court Sport Variation (BUILD:296-297 requirement): - Added Sport and SportVariation types to courts.ts - Created getSports() API client for GET /admin/sports - Updated Court and CourtRequest types with sport_variation_id field - Added sport variation dropdown to court creation modal - Auto-selects first variation for new courts - Sport type locked after creation (disabled in edit mode) - Mock data updated with sport_variation_id values Profile Bug Fix: - Fixed click-to-edit crash when field values are empty/undefined - Added null checks before calling .trim() in hasFieldValue() and EditableField - Error: "Cannot read properties of undefined (reading 'trim')" - Now safely handles empty string values UI Details: - Sport dropdown shows "Padel - Indoor", "Padel - Outdoor", etc. - Loading spinner while fetching sports - Validation error if no sport variation selected - Form includes both name and sport_variation_id in POST request Backend Brooke message: Court creation now requires sport_variation_id parameter	1 month ago
Guillermo Pages	a61e64ded0	feat(admin): align UI with Backend Brooke Phase 2 contracts, flip mocks to real endpoints ... Phase 2 Integration Updates: - Profile UI: Read/write address and contact fields from settings.address/settings.contact JSONB structure - Court dependencies: Updated modal to show 3 counts (slot_definitions, slot_instances_future, slot_instances_booked) - Error codes: Fixed duplicate court check to use court_name_duplicate (matches backend) - Mock flags: Flipped all 9 USE_MOCKS flags to false (courts.ts x7, materialisation.ts x2) Profile Tab (ClubProfileTab.tsx): - Read address fields from profile.settings?.address?.line_1 etc. - Read contact fields from profile.settings?.contact?.phone etc. - Write to settings structure preserving existing settings - Added Info icon tooltips: "Stored in settings until native fields ship" - Removed Integration section (provider/remote_club_id not in API) Court Dependencies Modal (ClubCourtsTab.tsx): - Display slot_instances_future count (was upcoming_bookings) - Display slot_instances_booked count (new field) - Updated deletion instructions for 3-count structure Types (courts.ts): - Created ClubProfileSettings interface for JSONB structure - Updated ClubProfile to use settings instead of flat fields - Updated CourtDependencies with court_id + 3 dependency counts - Updated ClubProfileUpdateRequest to support settings API Clients: - courts.ts: Updated mock data to match API contracts (settings structure, 3 counts, court_name_duplicate) - materialisation.ts: Flipped USE_MOCKS to false for real backend integration Integration Ready: - All contract mismatches resolved - Build succeeds - Ready for Phase 1 smoke tests against BUILD:290-291 Related: Backend Brooke BUILD:290 (courts CRUD) + BUILD:291 (club profile PATCH) Contract references: docs/owners/payloads/court-api-contract.md, club-profile-api-contract.md	1 month ago
Guillermo Pages	251b849500	feat(admin): add materialisation trigger/status UI + court management infrastructure ... Phase 1 continuation + Phase 2 preparation per Chief Cole request (Chief_Cole-20251107102650) Materialisation UI (Phase 1 continuation): - Created MaterialisationStatusPanel component with 5 states (never run, success, running, failed, rate limited) - Polling strategy: 3-second intervals while job running - Rate-limit countdown timer with live updates - Idempotency key generation (UUID v4) for manual triggers - Mock data for development with state cycling - Integrated into slot definitions page between header and table - TypeScript types: MaterialisationStatus, MaterialisationTriggerRequest/Response, helpers - API client with mock implementation (USE_MOCKS flag) - Professional slate theme consistent with existing UI Court Management Infrastructure (Phase 2 preparation): - Created TypeScript types for courts and club profile - Court types: Court, CourtRequest, CourtDependencies - Profile types: ClubProfile, ClubProfileUpdateRequest - Common timezones list (40+ IANA zones) - Validation helpers (email, URL) - API client with full CRUD mocks: - getClubProfile, updateClubProfile - getCourts, createCourt, updateCourt, deleteCourt - getCourtDependencies (cascade blocking) - Mock data: 3 courts, full profile, dependency simulation - In-memory mock state management Implementation ready for: - Next: Club detail tab navigation (Profile/Courts/Slot Definitions) - Next: Profile tab with edit form - Next: Courts tab with add/edit/delete modals Build tested and passed (npm run build successful)	1 month ago