diff --git a/.github/ISSUE_TEMPLATE/base44_backend_validation.md b/.github/ISSUE_TEMPLATE/base44_backend_validation.md deleted file mode 100644 index ce208582..00000000 --- a/.github/ISSUE_TEMPLATE/base44_backend_validation.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -name: 'API Validation and Backend Update from Base44' -about: 'Use this template to analyze Base44 API changes and update our backend.' -title: '[Base44] API Changes Validation and Backend Update' -labels: 'enhancement, platform:backend, sred-eligible' ---- - -### 🎯 Objective -Analyze API and event changes from the latest Base44 export, validate their impact on our system, and update our backend (Data Connect, Cloud Functions) to ensure compatibility and integrate new functionalities. - ---- - -### 🔬 SR&ED Justification -* **Technological Uncertainty:** What is the impact of Base44 API schema changes (deprecated fields, new types, modified logic) on our Data Connect GraphQL schemas and Cloud Functions logic? Is there a risk of data corruption or contract breakage with client applications? -* **Systematic Investigation:** We will perform a differential analysis ("diff") of the API schemas, update our GraphQL schema accordingly, adapt business logic in connectors and functions, and then deploy to a test environment to validate end-to-end integration. - ---- - -### 💻 Technical Implementation Notes -Refer to the [API Documentation Maintenance Guide](docs/06-maintenance-guide.md) for detailed steps on how to update the backend from a Base44 export. - ---- - -### ✅ Acceptance Criteria -- [ ] The impact analysis of API changes is documented. -- [ ] Data Connect schemas and connectors are updated. -- [ ] Affected Cloud Functions are updated. -- [ ] Changes are deployed and validated in the `dev` environment. -- [ ] **Given** an operation (query or mutation) affected by the changes is executed, **when** the API is called, **then** it should return a correct and consistent response with the new schema, without errors. diff --git a/.github/ISSUE_TEMPLATE/base44_frontend_update.md b/.github/ISSUE_TEMPLATE/base44_frontend_update.md deleted file mode 100644 index 4bfaad91..00000000 --- a/.github/ISSUE_TEMPLATE/base44_frontend_update.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -name: 'Frontend Update from Base44' -about: 'Use this template to integrate the latest frontend changes from a Base44 export.' -title: '[Base44] Frontend Update from Export' -labels: 'enhancement, platform:web, sred-eligible' ---- - -### 🎯 Objective -Integrate the latest UI changes (components, queries, mutations) generated from the most recent Base44 export to keep our application up-to-date with the platform schema. - ---- - -### 🔬 SR&ED Justification -* **Technological Uncertainty:** How will the newly generated queries and mutations integrate with our existing state management and caching logic (e.g., TanStack Query) without introducing regressions or performance issues? -* **Systematic Investigation:** We will implement the new generated hooks, refactor affected components, and perform performance and non-regression tests to validate that the integration is robust and performant. - ---- - -### 💻 Technical Implementation Notes -Refer to the [API Documentation Maintenance Guide](docs/06-maintenance-guide.md) for detailed steps on how to update the frontend from a Base44 export. - ---- - -### ✅ Acceptance Criteria -- [ ] The Data Connect generated code is updated to the latest version. -- [ ] All components and pages affected by the changes are updated and function as expected. -- [ ] The code is linted and formatted correctly. -- [ ] The functionality is manually tested and works in the `dev` environment. -- [ ] **Given** I navigate to a page affected by the update, **when** data is loaded, **then** I should see the new data structured correctly with no console errors. diff --git a/.github/ISSUE_TEMPLATE/sred_task.md b/.github/ISSUE_TEMPLATE/sred_task.md deleted file mode 100644 index 05c5c782..00000000 --- a/.github/ISSUE_TEMPLATE/sred_task.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -name: SR&ED Task -about: Use this template for a new development task that may be eligible for SR&ED. -title: '[Category] Short description of the task' -labels: 'sred-eligible' ---- - -### 🎯 Objective -*(A concise, one-sentence summary of what this issue aims to accomplish. Ex: "Connect the Events page to the development backend.")* - ---- - -### 🔬 SR&ED Justification -* **Technological Uncertainty:** What is the technical challenge or unknown we are trying to solve? *(Ex: "Can the Data Connect generated SDK be performantly integrated with TanStack Query in our existing React architecture?")* -* **Systematic Investigation:** What is our planned approach to resolve this uncertainty? *(Ex: "We will build a PoC on the Events page, measure load times, and document the optimal integration pattern.")* - ---- - -### 💻 Technical Implementation Notes -* **Key Files to Modify:** `file1.js`, `file2.gql`, etc. -* **Suggested Approach:** A brief description of the technical steps. *(Ex: "1. Define `listEvents` query in GraphQL. 2. Generate the SDK. 3. Create a `useEvents` hook that uses `useQuery`...")* -* **Considerations:** Potential pitfalls or points to watch out for. *(Ex: "Ensure loading and error states are handled correctly.")* - ---- - -### ✅ Acceptance Criteria -*A checklist of what must be true for the task to be considered "done."* -- [ ] The code is implemented following the technical notes. -- [ ] All new code is linted and formatted. -- [ ] The functionality is tested and works as expected in the `dev` environment. -- [ ] *(Example for a UI task)* **Given** I am on the Events page, **when** the page loads, **then** I should see a list of events coming from the `dev` backend. diff --git a/.reference/base44-entity-schemas.md b/.reference/base44-entity-schemas.md deleted file mode 100644 index 33b62789..00000000 --- a/.reference/base44-entity-schemas.md +++ /dev/null @@ -1,80 +0,0 @@ -# Base44 Entity Schemas Reference - -This document serves as a developer reference for the original data schemas from the Base44 backend. It is used to ensure feature parity and data integrity during the migration to the new GCP/Firebase backend. - ---- - -## User Schema - -``` -role (text, required) -- The role of the user in the app -- Options: admin, user - -email (text, required) -- The email of the user - -full_name (text, required) -- Full name of the user - -user_role (text) -- User's role in the system -- Options: admin, procurement, operator, sector, client, vendor, workforce - -company_name (text) -- Company or organization name - -profile_picture (text) -- URL to profile picture - -phone (text) -- Phone number - -address (text) -- Address - -preferred_vendor_id (text) -- ID of the client's preferred/default vendor - -preferred_vendor_name (text) -- Name of the client's preferred vendor - -backup_vendor_ids (array) -- List of backup vendor IDs - -dashboard_layout (object) -- User's customized dashboard layout preferences (legacy, kept for backward compatibility) -- widgets (array): Ordered list of visible widgets -- hidden_widgets (array): List of hidden widgets -- layout_version (text): Layout version for migration - -dashboard_layout_client (object) -- Client dashboard layout -- widgets (array) -- hidden_widgets (array) -- layout_version (text) - -dashboard_layout_vendor (object) -- Vendor dashboard layout -- widgets (array) -- hidden_widgets (array) -- layout_version (text) - -dashboard_layout_operator (object) -- Operator dashboard layout -- widgets (array) -- hidden_widgets (array) -- layout_version (text) - -dashboard_layout_workforce (object) -- Workforce dashboard layout -- widgets (array) -- hidden_widgets (array) -- layout_version (text) - -preferences (object) -- User preferences and settings -- theme (text): Default: "light", Options: light, dark -- notifications_enabled (boolean): Default: true -- email_notifications (boolean): Default: true -```