-
Notifications
You must be signed in to change notification settings - Fork 984
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(req): add restifyDone event #1740
Conversation
docs/api/request-events.md
Outdated
2) An error was returned to `next()`, and the corresponding error events have | ||
been fired for that error type | ||
|
||
The signature is for the `restifyDone` event is as follows: |
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.
s/is/''
The signature is for the `restifyDone` event is as follows: | ||
|
||
```js | ||
function(route, error) { } |
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.
Any reason not to match the API of server after?
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.
I just thought it would look strange that we pass req in a req event...
|
||
// restifyDone is emitted at the same time when server's after event is emitted, | ||
// you can find more comprehensive testing for `after` lives in server tests. | ||
test('should emit restifyDone event when request is fully served', function(t) { |
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.
Should we add a test for next(err)
too?
Emit a
restifyDone
event on thereq
object when the request is "fully served" (see docs in this PR).