When a content type changes, our apps (Next.js and Angular) just breaks, nasty error no information on how to fix it etc. We can do better than that.
We can make our UI components a bit more resilience that when the data they are expecting changes... instead of crashing the app it just shows an error message, that can lead the developer to find a solution or fix.
Not sure which one of these will fix our problems.
Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
### Acceptance Criteria
- [ ] Implement Error Handling: Equip all UI components with error boundaries to manage errors gracefully and don't crash the app.
- [ ] Display Error Messages: Show user-friendly error messages in the UI components when exceptions occur due to data type changes.
- [ ] Dev mode: Errors should only show in dev mode in prod, blank.
- [ ] Log Error Details: Add an error message con the `console.log` or the server log
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
To write a good error message:
Be Clear and Specific: Clearly state the problem.
Provide Guidance: Suggest possible solutions or next steps.
Be Concise: Keep the error message brief and to the point.
Parent Issue
TBD
Task
When a content type changes, our apps (Next.js and Angular) just breaks, nasty error no information on how to fix it etc. We can do better than that.
We can make our UI components a bit more resilience that when the data they are expecting changes... instead of crashing the app it just shows an error message, that can lead the developer to find a solution or fix.
Not sure which one of these will fix our problems.
Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
To write a good error message:
Assumptions & Initiation Needs
N/A
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
History