Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

JavaScript Build a REST API With Express Completing and Testing the API Connecting the API and Database

'next()' vs. 'return next()'

In the router.param() for qID, Andrew writes 'return next()'

Why, in the router.param for aID, does he simple use 'next()'?

Is there a reason we're using the return keyword above? And in each of the error handling if statements? Why is it not used in the router.param() for aID?

1 Answer

Daniel Totten
seal-mask
.a{fill-rule:evenodd;}techdegree seal-36
Daniel Totten
Full Stack JavaScript Techdegree Graduate 21,008 Points

I'm not 100% sure why it isn't in the param method for the aID (possibly just a small oversight), but for all the other next() instances, using the return keyword ensures that the function will stop executing and move on to the next middleware, avoiding any unintentional misfiring of code below it.