You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the motivation / use case for changing the behavior?
I'm not sure what I can expect from these parameters without type information. Is there a reason for them all to explicitly be any? If it's because Nest isn't tied to a specific framework, then perhaps there could be separate ExpressMiddlewareFunction, KoaMiddlewareFunction, etc.?
If there is a simple way for me to annotate the middleware function myself I can do that, but it would be cool if the MiddlewareFunction was already annotated.
Environment
Nest version: 5.0.1
For Tooling issues:
- Node version: 10.3.0
- Platform: Mac
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
The MiddlewareFunction interface doesn't contain type information for the parameters:
Expected behavior
The params of MiddlwareFunction to be stongly typed, something like:
What is the motivation / use case for changing the behavior?
I'm not sure what I can expect from these parameters without type information. Is there a reason for them all to explicitly be any? If it's because Nest isn't tied to a specific framework, then perhaps there could be separate
ExpressMiddlewareFunction
,KoaMiddlewareFunction
, etc.?If there is a simple way for me to annotate the middleware function myself I can do that, but it would be cool if the
MiddlewareFunction
was already annotated.Environment
The text was updated successfully, but these errors were encountered: