3 ms·
I've been hesitant to switch to something that demands custom type declarations, because we're already autogenerating a lot of types/interfaces with express-ope
by joshAg 7y ago
I've been hesitant to switch to something that demands custom type declarations, because we're already autogenerating a lot of types/interfaces with express-openapi (we lean heavily on their request and response validators, too but those don't cover all the types we make), and getting that to play nicely with custom declarations is not my idea of fun. But for the types that aren't tied back to an json-endpoint (we have a few endpoints where we're getting xml or csv or xlsx and a few db<-->backend only interfaces), this looks like a great solution.
Typescript-is looks like it might have an overall edge, though, because we can use it on the autogenerated types as well with almost no hassle.