-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Option to accept unhandled routes #224
Comments
@Cactusbone thanks for the question.
let me know if this helps or if you run into any issues. we certainly, want me to ensure this scenario works for you. feel free to reach on our gitter channel as well |
@cdimascio thanks for the answer I'm trying to add openapi-validator gradually in an already existing project, so we have a lot of existing routes, and we'd like to only use openapi-validator for specific routes, without breaking our usual REST route organization, mutiple validators example use a distinct baseUrl for each validator instance. I'll try overlapping routes when I'll need them though :) Right now i'll use basePath, and try to call install after every other route is configured |
@Cactusbone That should work. closing this issue for now. If you find the existing functionality doesn't suit your needs, please re-open and we'll look to provide a better solution. thanks for your interest in the project |
ignorePaths is kinda hard to maintain though, watchPath regexp or a flag to allow unknown routes would be easier to use in my case |
For routes not defined in specs, I'd like to be able to not have a failure, for examples when routes are added after OpenApiValidator.install call (in my case asynchronously), or to be able to have multiple specs with overlapping baseUrl (in multiple OpenApiValidator instances), to sort code to my liking.
It this already possible ?
The text was updated successfully, but these errors were encountered: