Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

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

Posted by Elliot Liebman
.a{fill-rule:evenodd;}techdegree seal-36
Elliot Liebman
Full Stack JavaScript Techdegree Graduate 20,304 Points

'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
Daniel Totten
.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.