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.

Sign up for GitHub

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

Jump to bottom

Optional nickname is required? #178

Closed
bfanger opened this issue Apr 4, 2013 · 3 comments
Closed

Optional nickname is required? #178

bfanger opened this issue Apr 4, 2013 · 3 comments

Comments

@bfanger
Copy link

bfanger commented Apr 4, 2013

In the https://github.com/wordnik/swagger-core/wiki/API-Declaration it says:

nickname. This is an optional field provided by the server for the convenience of the UI and client code generator."

But swagger-ui crashes with the message: SwaggerOperations must have a nickname.
@fehguy
Copy link
Contributor

fehguy commented Apr 4, 2013

Yes, I will update that in the wiki. It technically could be auto-generated by the UI if it doesn't exist but that's not supported as you found.

https://github.com/wordnik/swagger-core/wiki/API-Declaration#apis

@fehguy fehguy closed this as completed Apr 4, 2013
@jackchi
Copy link

jackchi commented Mar 4, 2014

Also, I found a discrepancy in the API-Declaration.
In the GitHub Wiki, it specifies "errorResponse" but in the actual api-docs, it is "responseMessages".
Could you please clarify?

@webron
Copy link
Contributor

webron commented Mar 4, 2014

The correct field is responseMessages. This should be clearer in the revamped spec documentation to be released soon.

reva2 pushed a commit to reva2/swagger-php that referenced this issue Apr 15, 2016
Generate a hint when the Operation->nickname is empty
ba63088 
The "optional" nickname is required by swagger-ui
swagger-api/swagger-ui#178
@snyk-bot snyk-bot mentioned this issue Nov 4, 2022
Open
@danielsan danielsan mentioned this issue Nov 6, 2022
Open
@danielsan danielsan mentioned this issue Dec 25, 2022
Open
@enjame enjame mentioned this issue Dec 25, 2022
Open
This was referenced Dec 29, 2022
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bfanger @webron @fehguy @jackchi