Route Forwarding: receive multiple arguments res.io.respond(a,b,c,...)
#73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I love the idea of Route Forwarding but somehow encounter a problem. I prefer pass result or error to browser with node style
[err, result, ...]
which is really common conventionbut it doesnt work with Route-Forwarding because express's
res.json
expect additional param as status code, sores.io.respond(null, data)
=>res.json(null, data)
just crash express.writing sth. like
res.io.respond(500, err)
works with current express.io but really sounds strange, so I send this PR to change this behavior. it does break backward compatibility but I believe it worth that