refactor: reorganize project module file structure#17
Merged
Conversation
- Add MeetingFormComponent with comprehensive form validation and tooltips - Create backend endpoints for meeting CRUD operations (POST/PUT/GET) - Add TypeScript interfaces for CreateMeetingRequest and UpdateMeetingRequest - Implement proper datetime conversion from 12-hour format to ISO - Integrate meeting form into modal component with create/edit modes - Add meeting creation functionality to dashboard with form modal - Update SupabaseService with meeting management methods - Fix time picker integration and validation Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Add comprehensive timezone list with 80+ timezones covering all regions - Implement form validation to ensure meetings are scheduled in the future - Add calendar date restriction to only allow dates from yesterday onwards - Default start date/time to current time + 1 hour (rounded to 15 min) - Show all validation errors when submit is clicked - Add minDate/maxDate support to calendar component wrapper - Create timezone constants in shared package with helper functions - Fix nested ternary expressions per linting rules - Update meeting type validation and default values Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Fix meeting_type default value to use 'None' instead of empty string - Ensure consistent default values across create and edit modes - Update form patchValue to handle meeting data properly Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
Implement comprehensive recurring meeting functionality with 6 predefined recurrence patterns: - Does not repeat (default) - Daily - Weekly on [current day] - Monthly on the [nth] [day] - Monthly on the last [day] - Every weekday Key features: - Dynamic options based on selected meeting date - Smart UI that only shows relevant options (no duplicate monthly options) - Proper memory management with takeUntilDestroyed() - Full TypeScript support with new MeetingRecurrence interface - Generates correct Zoom API recurrence objects - Edit support for existing recurring meetings Technical implementation: - Added RecurrenceType enum to shared enums package - Enhanced MeetingRecurrence interface with proper typing - Updated CreateMeetingRequest and UpdateMeetingRequest interfaces - Intelligent date calculation for monthly recurrence patterns - Subscription cleanup to prevent memory leaks Addresses LFXV2-138: Add Recurring Meeting Options to Meeting Form Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Asitha de Silva <asithade@gmail.com>
…nums folder Move MeetingVisibility and MeetingType enums from interfaces to the proper shared enums folder structure for better organization and consistency. 🤖 Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Add DELETE endpoint with recurrence handling support - Enhanced confirmation dialog with meeting details preview - Options for recurring meetings (single occurrence vs entire series) - Dynamic menu items that exclude edit option for past meetings - Proper loading states and error handling throughout deletion flow - Complete backend and frontend integration with proper validation 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Create MeetingDeleteConfirmationComponent for better HTML control - Add shared RadioButtonComponent following checkbox pattern - Replace inline HTML confirmation with structured component - Implement form-controlled radio buttons for recurring meeting options - Clean up meeting dashboard by removing multiple helper methods - Add proper TypeScript interfaces for component data/results 🤖 Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Move meeting deletion logic from dashboard to confirmation component - Add comprehensive error handling with specific HTTP status messages - Implement loading states with disabled buttons and spinner icons - Add success/error toast notifications for user feedback - Keep dialog open on error to allow retry, close only on success - Simplify meeting dashboard by removing deletion state management - Improve separation of concerns and component self-containment 🤖 Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Add 'future' delete type for recurring meetings to delete from current date forward - Hide radio button options for past meetings (only show single delete option implicitly) - Update backend and frontend services to support new 'future' delete type - Add conditional UI logic based on meeting start_time vs current time - Enhanced warning messages for different delete scenarios - Improved UX by showing only relevant options based on meeting timing 🤖 Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
Signed-off-by: Asitha de Silva <asithade@gmail.com>
…port - Add edit meeting functionality to meeting dashboard component - Create RecurringMeetingEditOptionsComponent for two-step edit flow - Support editing single occurrence vs future occurrences for recurring meetings - Hide recurrence and meeting settings when editing single occurrence only - Fix interface alignment between Create/Update requests and database schema - Remove end_time field and calculate from start_time + duration - Add recording_access field to meeting form and interfaces - Fix AI summary field initialization with nullish coalescing - Update backend routes and services to support editType parameter - Improve form field visibility based on edit context 🤖 Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Add restricted field as a boolean toggle in meeting settings - Update form group to include restricted control - Add restricted field to meeting data submission - Initialize restricted field when editing existing meetings - Hide restricted toggle when editing single occurrence only The restricted toggle allows marking meetings with limited access where only authorized participants can join. 🤖 Generated with [Claude Code](https://claude.ai/code) Signed-off-by: Asitha de Silva <asithade@gmail.com>
Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Add participant API endpoints (GET, POST, DELETE) for meeting participants - Create AddParticipantFormComponent with form validation and error handling - Create ParticipantListComponent with delete functionality and confirmation dialogs - Create ParticipantManagementModalComponent with Inplace toggle for adding participants - Create shared InplaceComponent wrapper for PrimeNG Inplace - Add participant management to meeting dashboard action menu - Integrate participant modal with meeting cards (opens when no participants) - Implement dashboard refresh when participants are modified - Add backend Supabase service methods for participant CRUD operations - Update meetings_with_committees view to include participant counts - Add proper error handling and loading states throughout 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Asitha de Silva <asithade@gmail.com>
Signed-off-by: Asitha de Silva <asithade@gmail.com>
Signed-off-by: Asitha de Silva <asithade@gmail.com>
Signed-off-by: Asitha de Silva <asithade@gmail.com>
Signed-off-by: Asitha de Silva <asithade@gmail.com>
- Create modular file organization with 5 main sections: dashboard, meetings, committees, mailing-lists, settings - Move route components to their respective section folders - Move section-specific components from shared/components to section-specific components folders - Update all import paths to reflect new structure - Update documentation to reflect new component placement guidelines This improves code organization by co-locating related components and reducing the shared components folder to only truly cross-cutting UI components. JIRA: LFXV2 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Asitha de Silva <asithade@gmail.com>
github-actions
bot
requested review from
andrest50,
audigregorie and
mauriciozanettisalomao
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR reorganizes the project module file structure to improve code organization and maintainability by creating a modular structure with 5 main sections (dashboard, meetings, committees, mailing-lists, and settings) and moving components from shared/components to their respective section-specific folders.
- Created new directory structure under
app/modules/project/with 5 main sections - Moved section-specific components from
shared/componentsto their respective section folders - Updated all import paths and added new TypeScript path aliases for services and pipes
- Added new meeting participant management functionality with API endpoints and UI components
Reviewed Changes
Copilot reviewed 42 out of 70 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/architecture/frontend/component-architecture.md | Added comprehensive documentation for the new modular file organization pattern |
| docs/architecture.md | Updated import path example to use new service alias |
| apps/lfx-pcc/tsconfig.json | Added new path aliases for @services and @pipes |
| apps/lfx-pcc/src/styles.scss | Added CSS custom property for p-inplace padding |
| apps/lfx-pcc/src/server/services/supabase.service.ts | Added methods for managing meeting participants |
| apps/lfx-pcc/src/server/routes/meetings.ts | Added API endpoints for participant management |
| apps/lfx-pcc/src/app/shared/services/meeting.service.ts | Added client-side methods for participant operations |
| apps/lfx-pcc/src/app/shared/components/inplace/inplace.component.ts | New wrapper component for PrimeNG inplace |
| Multiple component files | Updated import paths to use new aliases and section-specific locations |
| apps/lfx-pcc/src/app/app.routes.ts | Updated route imports to reflect new structure |
apps/lfx-pcc/src/app/modules/project/meetings/components/meeting-form/meeting-form.component.ts
Show resolved
Hide resolved
apps/lfx-pcc/src/app/modules/project/meetings/components/meeting-form/meeting-form.component.ts
Show resolved
Hide resolved
apps/lfx-pcc/src/app/modules/project/meetings/components/meeting-form/meeting-form.component.ts
Show resolved
Hide resolved
apps/lfx-pcc/src/app/modules/project/meetings/components/meeting-form/meeting-form.component.ts
Show resolved
Hide resolved
jordane
approved these changes
Jul 30, 2025
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
2 participants
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.
Summary
Changes
app/modules/project/with 5 main sectionsshared/componentsto section-specificcomponentsfoldersBenefits
Test plan
JIRA: LFXV2
🤖 Generated with Claude Code