Runtime validation beyond type assertions
Removing type assertions led me to separate failure handling for API responses, URLs, and forms. A narrower type does not necessarily mean a safer runtime value.
#zod
Posts with this tag.
Letting failed sections recover with Error Boundaries
One failed list query removed the menu and header too. I changed query placement along with Error Boundaries so a failed table or filter could be retried in place.
Sharing a program form across two admin apps
Two admin apps shared program inputs but had different submission flows. I separated field types and API transformations while deciding what to share.
Separating state and steps in a review form
Moving review writing to RHF and Zod also meant reconnecting treatment selection. I changed the sheet to cancel on close and write selections to the form only after confirmation.
Moving reservation form state from Zustand to React Hook Form
Adding a family member left reservation dates behaving as if the old participant count still applied. I separated the server's family list from user selections and moved ongoing edits into React Hook Form.