add next() to express template, closes #1593

[ericwooley]

closes #1593

All Submissions:

• [X] Have you followed the guidelines in our Contributing document?
• [X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [X] Have you written unit tests?
• [ ] Have you written unit tests that cover the negative cases (i.e.: if bad data is submitted, does the library respond properly)?
• [X] This PR is associated with an existing issue?

Closing issues

Put closes #XXXX (where XXXX is the issue number) in your comment to auto-close the issue that your PR fixes.

If this is a new feature submission:

• [ ] Has the issue had a maintainer respond to the issue and clarify that the feature is something that aligns with the goals and philosophy of the project?

Potential Problems With The Approach

Technically this could be considered a breaking change, but IMO it should be considered a bug fix.

Test plan

I added an in memory boolean to the express server, added routes to check/modify that boolean, and a middleware which modifies the bool after the register routes. The tests first set that boolean to false, then, after a route has run through tsoa, checks that the boolean was modified by the middleware.

[ericwooley]

Hi @lukeautry

Just wanted to check in and see if this got lost in the shuffle