1–7 of 7 posts
I’ve been working on a node.js package that generates typescript types from API responses. I would love to know what you think and would appreciate any feedback!
Show HN: API Typegen – Generate TypeScript types from API responses
github.com
Does it add any new features?
Is there any benefit over using this versus an industry standard like OpenAPI/Swagger? Does it add any new features?
Is there any benefit over using this versus an industry standard like OpenAPI/Swagger? Does it add any new features?
Tbh, there is no benefit of using this package if the API you are working with has an openapi spec, as there are other great libraries to help you generate accurate types such as https://github.com/openapi-ts/openapi-typescript . But I made this package to use when working with external apis that don't have an available spec.
Maybe good to describe that use case in the README.
Earlier quoted context omitted.
Tbh, there is no benefit of using this package if the API you are working with has an openapi spec, as there are other great libraries to help you generate accurate types such as https://github.com/openapi-ts/openapi-typescript . But I made this package to use when working with external apis that don't have an available spec.
Got it, that makes sense. Maybe good to describe that use case in the README.
It would be interesting to know how it works for you in a real project. I often have to create types for undocumented endpoints, but it's always a guessing game. Without a proper spec or reading the source code, it's impossible to know if a field is nullable or not, or to distinguish a real text field from a string based enum