add ability to include custom swagger extensions in config

[gwprice115]

All Submissions:

More than happy to write tests and stuff once I get confirmation this is the right approach

• [ ] 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?
• [ ] 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 closes #1532 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

Test plan

[TristanSpeakEasy]

Would love to see this go in will make our lives much easier

[WoH]

This would probably require us to also be able to use a .tsoa.js as config file instead of the tsoa.json, if you don't call generateSwagger directly, but use the cli. (And also live in the spec config) Also, it should be bw-compat if not provided.

[gwprice115]

This would probably require us to also be able to use a .tsoa.js as config file instead of the tsoa.json, if you don't call generateSwagger directly, but use the cli. (And also live in the spec config) Also, it should be bw-compat if not provided.

gotcha makes sense--would you accept it if it was a static reference similar to how auth is specified?

[WoH]

Yes

[github-actions[bot]]

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days