kubero-dev / kubero-dev/kubero
use zod for better typings
Open
Nobody has claimed this yet.
Idea/discussion
UI
- Dominant language
- TypeScript
- Stars
- 4.4k
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Description
Since the API is built using typescript, hence using zod to enforce better types especially for type checking he results of API calls might be a good idea.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the TypeScript API entry points and the current handling of API-call results. Define the scope for adopting zod, including which responses require runtime validation and how this fits the existing type checks. Done means the agreed API results are validated with zod and the relevant type-checking behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100