Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate using Libraries that create an schema and type #75

Open
1 task
M-jerez opened this issue Sep 10, 2023 · 0 comments
Open
1 task

Investigate using Libraries that create an schema and type #75

M-jerez opened this issue Sep 10, 2023 · 0 comments
Milestone

Comments

@M-jerez
Copy link
Contributor

M-jerez commented Sep 10, 2023

Seem that the Typescript Community and ten Typescript team itself favors Libraries that create an schema and later you can get a type from it. ie, zod, valibot etc, rather than libraries that att metadata to types at ryntime.

More info here: https://github.com/akutruff/typescript-needs-types. mentioned repo is trying for the Typescript team to include types at runtime but from some comments from the typescript team, that never gonna happen.

Also using a typescript transformer can make things more complicated when using new JS runtimes like Deno and Bun, that includes an standard typescript compiler.

So to summarize, look like the community prefers schema libraries like zod rather than add metadata for types at runtime.

  • explore using libraries like zod or valibot and make it configurable
@M-jerez M-jerez added this to the towards V1 milestone Sep 15, 2023
@M-jerez M-jerez changed the title Moving away from compiled type metadata and use Libraries that create an schema and type Investigate using Libraries that create an schema and type Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant