[enhancement] reuse response description
See original GitHub issueHello, First of all I want to thanks the openAPI community. I really appreciate the standard, it really helps the communication between back and front developers. I tried to reuse response description in this way:
...
responses:
'200':
allOf:
- $ref: '../index.yaml#/components/responses/200Ok'
It seems that it’s not a valid syntax even if it works well on swagger-ui I think that it will be helpful to share the response description between different responses, avoiding to repeat the same message everytime.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Reuse and Improve - | Principles for Digital Development
Reuse means assessing what resources are currently available and using them as they are to meet program goals. Improve means modifying existing tools,...
Read more >combining use cases and event response lists for reuse and ...
This report describes an approach to combining Use Cases with elements from Event Response Lists to help improve requirements understanding.
Read more >Reusable Choices - Qualtrics
Reusable choices allow you to save a list of choices in your survey that you can reuse in more than one question. If...
Read more >Enhancing Reuse and Resource Recovery of Electrical and ...
Enhancing reuse and resource recovery of electrical and electronic equipment with reverse logistics to meet carbon reduction targets.
Read more >Enhancing Data Reuse - Feature Extraction - ResearchGate
Enhancing Data Reuse: Standardized Description of the Feature Extraction Process to Transform Raw Data into Meaningful Information.
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
I really wish Description wasn’t required.
@webron @whitlockjc another
$ref
-with-stuff issue to add to that pile.