-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Method level reader extensions #1513
Conversation
Not entirely sure what's your end goal here, but you should definitely add a test for it (which would also explain your case). |
I added example as you asked. In short lets assume that come company created set of annotation which could be used on method level e.g. "@VendorFunnyAnnotation". If it is used this indicates that that method could return some error code and we would like to add that error code to swagger documentation. |
@frantuma can you review this please? |
done |
Upvote this pull request! It really simplifies unobtrusive tuning of documentation generation process. |
+1 |
I re-base it once again. Please merge it. |
Time 😕 @frantuma since you reviewed it in the past, feel free to merge if you feel confident about it. |
It should be possible to enrich swagger model by vendor based extensions stored on operation level. To do that we need to add extension point when operation is processed and method context exists. This allow to process e.g. some vendor annotation which are stored on method level and could be used by documentation.