Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug in parser - doesn't allow summary and description after path
See original GitHub issueI’m pretty sure that I’ve found a bug in the parser.
If you have a summary and/or description after the path in a definition as in this example from the OpenApi definition here https://swagger.io/docs/specification/paths-and-operations/
paths:
/users/{id}:
summary: Represents a user
description: >
This resource represents an individual user in the system.
Each user is identified by a numeric `id`.
get:
...
then the parser will fail. Remove that summary and description and it passes correctly.
(it is correctly happy with summary and description after the verb, but consistently fails if they exist after the path and before the verb).
Regards,
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have now tried with the latest version and the problem is resolved. Thanks!
Have you tried with latest version (13.1.5)?