Skip to content
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

Disable appending of Using<Method> #1066

Closed
rkaltreider opened this issue Nov 24, 2015 · 10 comments
Closed

Disable appending of Using<Method> #1066

rkaltreider opened this issue Nov 24, 2015 · 10 comments
Labels
Milestone

Comments

@rkaltreider
Copy link

How can i disable the appending of my methods with

Using<Method>

. All methods in my swagger doc have getPartnersUsingGet or similar. I want to get rid of that.

@rkaltreider rkaltreider changed the title Disable appending of Using<Methof> Disable appending of Using<Method> Nov 24, 2015
@gionn
Copy link

gionn commented Dec 1, 2015

http://springfox.github.io/springfox/docs/current/#docket-spring-java-configuration

5.5.2. Configuring the output of operationId in a Swagger 2.0 spec

@dilipkrish
Copy link
Member

@rkaltreider There is not a way to get rid of that ... yet. I'll see how we can address that in 2.3 if possible. However keep in mind that you will end up with names like someOperation_1, someOperation_2 etc. if there are multiple endpoints with the same nickname

@gionn I'll fix the documentation to reflect that.

@dilipkrish dilipkrish added this to the 2.3.0 milestone Dec 1, 2015
@rkaltreider
Copy link
Author

That sounds perfectly reasonable to me. I have taken the time to ensure all nicknames are unique and self descriptive. If I fail to solidify the uniqueness. I would expect it to make it unique however it sees fit. Thank you!

Sent from my iPhone

On Dec 1, 2015, at 10:26 AM, Dilip Krishnan <[email protected]mailto:[email protected]> wrote:

@rkaltreiderhttps://github.com/rkaltreider There is not a way to get rid of that ... yet. I'll see how we can address that in 2.3 if possible. However keep in mind that you will end up with names like someOperation_1, someOperation_2 etc. if there are multiple endpoints with the same nickname

@gionnhttps://github.com/gionn I'll fix the documentation to reflect that.

Reply to this email directly or view it on GitHubhttps://github.com//issues/1066#issuecomment-161000947.

@rajeshkamal5050
Copy link

Thanks @dilipkrish for the fix which I assume also fixes - #880 #990

@dilipkrish
Copy link
Member

👍

@rkaltreider
Copy link
Author

When do you think the next version will be released? I am anxious to upgrade!

Sent from my iPhone

On Dec 8, 2015, at 4:39 PM, Dilip Krishnan <[email protected]mailto:[email protected]> wrote:

[:+1:]

Reply to this email directly or view it on GitHubhttps://github.com//issues/1066#issuecomment-163025790.

@dilipkrish
Copy link
Member

Its already released see here for details 2.3.0

@g-bon
Copy link

g-bon commented Jun 13, 2018

Apologies for resuscitating this old discussion. Is the solution to this the use of @ApiOperation to specify a different nickname on every operation or is there a way to disable this behavior completely? Thanks

@dilipkrish
Copy link
Member

@g-bon You can write you own OperationNameGenerator however keep in mind you may need to take some hints from CachingOperationNameGenerator in order to guarantee unique operation names.

@g-bon
Copy link

g-bon commented Jun 14, 2018

Thank you sir!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants