We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If you "hover" one of our Request or Reply objects, they are overcrowded and hard to understand, and this is an expectation for a good DX in TypeScript:
Request
Reply
vs alternatives:
I'm not sure how we could improve this, because we allow a great degree of flexibility, but this has never been on our radar before.
The text was updated successfully, but these errors were encountered:
cc @climba03003
Sorry, something went wrong.
It can be done by grouping the generic and resolved to a single type. When we passing around it won't be a very long chain of generic.
I have tried once to compact the generic argument but no luck. The base types is really better to type as unknown to accept any variant.
unknown
To be fair, it still provide the information of what is the expected types in the later line.
No branches or pull requests
If you "hover" one of our
Request
orReply
objects, they are overcrowded and hard to understand, and this is an expectation for a good DX in TypeScript:vs alternatives:
I'm not sure how we could improve this, because we allow a great degree of flexibility, but this has never been on our radar before.
The text was updated successfully, but these errors were encountered: