Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Document req.next #728

Open
crandmck opened this issue Nov 2, 2016 · 2 comments
Open

Document req.next #728

crandmck opened this issue Nov 2, 2016 · 2 comments
Labels
docs Issues/pr concerning content help wanted

Comments

@crandmck
Copy link
Member

crandmck commented Nov 2, 2016

Per discussion in TC meeting we should doc req.next with some disclaimer about using it.
@crandmck
Copy link
Member Author

crandmck commented Nov 8, 2016

@dougwilson I recall that we discussed this, but not the details. What kind of disclaimer should we include with the doc for this function?

@dougwilson
Copy link
Contributor

A disclaimer probably saying that req.next should only be used as a last resort, and that there are various edge cases where it may not actually refer to what a user would think of as next(). Passing around callbacks would be recommended over this.

@bjohansebas bjohansebas added help wanted docs Issues/pr concerning content labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs Issues/pr concerning content help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dougwilson @crandmck @bjohansebas