Describe the problem and the solution you'd like
This is related to #415 . Zod is pretty standard for data validation for forms and for validating data from external APIs. Using zod to create schemas and using z.infer to create types from those is a nice pattern to use for data handling and complements the fetch handling developed on grants.gov.
The CMS-RASS challenge repo provides an example: https://github.com/navapbc/bid-fed-cms-rass-tech-challenge/tree/main/rass-web/src
lib/fetch // for fetch handling and error throwing
services/fetch // for adding individual API endpoints
schemas // for zod schemas
types/api // for types inferred from zod schemas
Alternatively we could adopt a library like orpc that handles the same functionality or standardize on a project like orval so are are adopting a more standard set of conventions.
Additional context
No response
Priority
None
Describe the problem and the solution you'd like
This is related to #415 . Zod is pretty standard for data validation for forms and for validating data from external APIs. Using zod to create schemas and using
z.inferto create types from those is a nice pattern to use for data handling and complements the fetch handling developed on grants.gov.The CMS-RASS challenge repo provides an example: https://github.com/navapbc/bid-fed-cms-rass-tech-challenge/tree/main/rass-web/src
Alternatively we could adopt a library like orpc that handles the same functionality or standardize on a project like orval so are are adopting a more standard set of conventions.
Additional context
No response
Priority
None