-
Notifications
You must be signed in to change notification settings - Fork 128
[Feature request] Typescript - Support generic request / response types #244
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
Comments
@jrbarnard great suggestion! Will give this some thought and keep you updated with my thoughts :) |
@naorpeled I would definitely love to see the support for generics. Have you had a chance to think about this? |
I'm planning on working on it, if anyone else wants to let me know 🙏 |
@naorpeled I have been using Just started learning TS so I may have missed something, apologies! |
Hey everyone, if anyone has time to take a look please let me know what you think as your guys' feedback is super important to me 🙏 |
Hey @antpingelli, |
Currently the
Request
andResponse
types are defined without any easy way to override them.I would like to be able to either supply generic response types or extended request types for a given route which allows me to have clearly defined types for the input/output of that route.
E.g if I have a route that should return a given shape of JSON, currently the
.json
method on response expectsany
, however if I could define the route with a Response type of a given shape, typescript would fail to compile if I had implemented the transformation in my route wrong.And for request extension, one use case is you have middleware that does your validation, so by the time you get to your route, you know the shape of your request. E.g which path params are present, or query string params are required and so on. It would be nice to be able to define a request extension for that route to avoid unnecessary checks or casting or non null assertions.
I'm happy to work on this and submit a couple of PRs, but would be keen to get some feedback first of all on how we'd want this to work / any considerations that need to be taken into account before hand.
A rough code example:
The text was updated successfully, but these errors were encountered: