-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Feature: Fallback routing #15
Labels
Comments
Merged
matzehecht
added a commit
that referenced
this issue
Aug 19, 2020
…(with opt-out) This changes the default behavior! The current behavior can be achieved by an opt-out. BREAKING CHANGE: If no tag is specified in a operation the mapped controller falls back to the index module. You can opt this out with fallbackControllerToIndex on AddFromSpecificationOpts. Closes #15
matzehecht
added a commit
that referenced
this issue
Aug 20, 2020
…(with opt-out) This changes the default behavior! The current behavior can be achieved by an opt-out. BREAKING CHANGE: If no tag is specified in a operation the mapped controller falls back to the index module. You can opt this out with fallbackControllerToIndex on AddFromSpecificationOpts. Closes #15
matzehecht
added a commit
that referenced
this issue
Aug 20, 2020
…(with opt-out) This changes the default behavior! The current behavior can be achieved by an opt-out. BREAKING CHANGE: If no tag is specified in a operation the mapped controller falls back to the index module. You can opt this out with fallbackControllerToIndex on AddFromSpecificationOpts. Closes #15
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fallback routing to index.ts as controller if no tag is specified:
ToDo:
The text was updated successfully, but these errors were encountered: