-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Improve swagger integration #507
Comments
What is your preferred fix for this? Would you like the ability to hide the endpoint from swagger? Just give it a name? |
Mmm... Now that you mention, both options are valid, is possible use both for more flexibility? maybe we can hide or show based on production/dev mode |
The best way to solve this problem from my point of view is to give you a way to provide a custom controller where you can do whatever annotations you want. This module shouldn't have any knowledge of Swagger. If this would work for you, let me know and I will see if I can come up with a solution. |
@willsoto yes, that will work too... Maybe that controller should implement some kind of interface provided by you, or extends your base controller or something like that to guarantee that the proper prom-client method is invoked |
@willsoto Thanks 🙌... |
@willsoto I got this error with
|
In the meantime, I've cut a v2.0.0 that only includes the commonjs version, so you should no longer see this issue. |
@willsoto yes, removing |
Thanks. You can upgrade to v2.0.0 and the issue will be resolved then. |
Hi... First of all, great job...
Can you provide a way to configure swagger integration and avoid this?... The ideal is having a way to customize the api tag
The text was updated successfully, but these errors were encountered: