-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
feat(): add ip route param #3249
Conversation
Pull Request Test Coverage Report for Build 5377
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice PR, well done!!!
From my side this feature is good to go. Though @iniel for future contributions, please create an issue before creating a pull request. This workflow is commonly done, so you do not waste time implementing something, which does not fit the core teams vision :)
Even though I really like this PR, I'm slightly concerned that adding more and more decorators that simply pick properties from the export const Ip = createParamDecorator((data, req) => req.ip); |
You are right in this concern. Basically I think most of the fields in request object are too low level to be used in handler business logic (like |
Thanks for your input @iniel. Sounds reasonable :) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Added ip param decorator for HTTP route handlers.
Does this PR introduce a breaking change?