6d698d9e1e
This commit introduces two new issue templates to streamline the process of updating the backend and frontend based on Base44 exports. The "API Validation and Backend Update from Base44" template is for analyzing API changes, updating the backend (Data Connect, Cloud Functions), and ensuring compatibility. It includes sections for objective, SR&ED justification, technical implementation notes, and acceptance criteria. The "Frontend Update from Base44" template is for integrating the latest UI changes (components, queries, mutations) from a Base44 export. It also includes sections for objective, SR&ED justification, technical implementation notes, and acceptance criteria.
1.6 KiB
1.6 KiB
name, about, title, labels
| name | about | title | labels |
|---|---|---|---|
| Frontend Update from Base44 | Use this template to integrate the latest frontend changes from a Base44 export. | [Base44] Frontend Update from Export | 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 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
devenvironment. - 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.