Support Open API 3.0
It would be great if this could be updated to support the Open API 3.0 spec. The main missing feature from Swagger 2.0 spec which is important for us is JSON encoded objects for query string parameters.
Posted by baseten on Jul 3, 2018, 11:47 AM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
support (Other)0 comments
I think of this as the kiosk economy.
support (Other)0 comments
What a goofy comment.
support (Other)0 comments
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
support (Other)0 comments
Compose support in WSLc
support (Other)0 comments
[RFC] Roadmap to v2.0
support (Other)0 comments
[Feature]: Add TurboQuant Support for KV Cache Quantization
support (Other)0 comments
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
support (Other)0 comments
Support Open API 3.0
basetenJul 3, 2018, 11:47 AM
It would be great if this could be updated to support the Open API 3.0 spec. The main missing feature from Swagger 2.0 spec which is important for us is JSON encoded objects for query string parameters.
Comments (0)
No comments yet. Start the discussion.