generated operation ids are very ugly
See original GitHub issueIt is true that operation ids are not required, but what we are currently generating is quite ugly. For example:
paths:
/test:
get:
# no operation id
parameters: []
responses:
200:
description: well done
Generates this for operationId
:
get-/test
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Swagger Codegen Duplicate Operation Ids With Additional ...
Also when omit the operationId the generated code is very very ugly the method names are unreadable. All reactions.
Read more >How is the operationId used from an OpenAPI schema?
operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in ......
Read more >Avoiding Permission Issues With Docker-Created Files
It's tedious and there is a better way: read on to learn learn how to build, configure and run your Docker containers correctly,...
Read more >How to dive into an ugly database? - DBA Stack Exchange
The first thing I do is create an Entity-Relationship Diagram (ERD). Sometimes you can simply describe the metadata with command-line tools but to...
Read more >Wind Power Information and Facts - National Geographic
Drawbacks include complaints from locals that wind turbines are ugly and noisy. The slowly rotating blades can also kill birds and bats, but...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It should
get_test
, yes. It’s not just without the slash, it’s also an underscore instead of a hyphen.Related issue https://github.com/swagger-api/swagger-js/issues/1013