GitHub - go-openapi/spec: openapi specification object model (original) (raw)
Navigation Menu
- GitHub Copilot Write better code with AI
- GitHub Advanced Security Find and fix vulnerabilities
- Actions Automate any workflow
- Codespaces Instant dev environments
- Issues Plan and track work
- Code Review Manage code changes
- Discussions Collaborate outside of code
- Code Search Find more, search less
Explore - Why GitHub
- All features
- Documentation
- GitHub Skills
- Blog
- By company size
- Topics
- Pricing
Provide feedback
We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Saved searches
Use saved searches to filter your results more quickly
Appearance settings
go-openapi / spec Public
- Notifications You must be signed in to change notification settings
- Fork102
- Star 410
openapi specification object model
License
Apache-2.0, Unknown licenses found
Licenses found
Apache-2.0 LICENSE Unknown license.go
410 stars 102 forks Branches Tags Activity
Notifications You must be signed in to change notification settings
Additional navigation options
Folders and files
Repository files navigation
OpenAPI v2 object model

The object model for OpenAPI specification documents.
FAQ
- What does this do?
- This package knows how to marshal and unmarshal Swagger API specifications into a golang object model
- It knows how to resolve $ref and expand them to make a single root document
- How does it play with the rest of the go-openapi packages ?
- This package is at the core of the go-openapi suite of packages and code generator
- There is a spec loading package to fetch specs as JSON or YAML from local or remote locations
- There is a spec validation package built on top of it
- There is a spec analysis package built on top of it, to analyze, flatten, fix and merge spec documents
- Does this library support OpenAPI 3?
No. This package currently only supports OpenAPI 2.0 (aka Swagger 2.0). There is no plan to make it evolve toward supporting OpenAPI 3.x. This discussion thread relates the full story.
An early attempt to support Swagger 3 may be found at: https://github.com/go-openapi/spec3
- Does the unmarshaling support YAML?
Not directly. The exposed types know only how to unmarshal from JSON.
In order to load a YAML document as a Swagger spec, you need to use the loaders provided by github.com/go-openapi/loads
Take a look at the example there: https://pkg.go.dev/github.com/go-openapi/loads#example-Spec
See also #164
- How can I validate a spec?
Validation is provided by the validate package
- Why do we have an
ID
field forSchema
which is not part of the swagger spec?
We found jsonschema compatibility more important: since
id
in jsonschema influences how$ref
are resolved. Thisid
does not conflict with any property namedid
.See also #23
About
openapi specification object model
Resources
License
Apache-2.0, Unknown licenses found
Licenses found
Apache-2.0 LICENSE Unknown license.go
Code of conduct
Stars
Watchers
Forks
Releases
Packages
No packages published