Skip to content

swagger

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History

swagger

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
core
core
 
 
testdata
testdata
 
 
README.md
README.md
 
 
externaldocs.go
externaldocs.go
 
 
externaldocs_nil_test.go
externaldocs_nil_test.go
 
 
factory_registration.go
factory_registration.go
 
 
info.go
info.go
 
 
info_getters_test.go
info_getters_test.go
 
 
info_validate_test.go
info_validate_test.go
 
 
marshalling.go
marshalling.go
 
 
operation.go
operation.go
 
 
operation_getters_test.go
operation_getters_test.go
 
 
operation_validate_test.go
operation_validate_test.go
 
 
parameter.go
parameter.go
 
 
parameter_test.go
parameter_test.go
 
 
paths.go
paths.go
 
 
paths_test.go
paths_test.go
 
 
reference.go
reference.go
 
 
reference_factory_test.go
reference_factory_test.go
 
 
response.go
response.go
 
 
response_validate_test.go
response_validate_test.go
 
 
roundtrip_test.go
roundtrip_test.go
 
 
security.go
security.go
 
 
security_validate_test.go
security_validate_test.go
 
 
swagger.go
swagger.go
 
 
swagger_test.go
swagger_test.go
 
 
swagger_validate_test.go
swagger_validate_test.go
 
 
tag.go
tag.go
 
 
tag_validate_test.go
tag_validate_test.go
 
 
upgrade.go
upgrade.go
 
 
upgrade_test.go
upgrade_test.go
 
 
walk.go
walk.go
 
 
walk_matching.go
walk_matching.go
 
 
walk_test.go
walk_test.go
 
 

README.md

Swagger

Swagger Parser

An API for working with Swagger Documents including: read, walk, create, mutate, and validate

Built by Speakeasy Release Go Doc
GitHub Action: Test Go Report Card Software License

Contributing

This repository is maintained by Speakeasy, but we welcome and encourage contributions from the community to help improve its capabilities and stability.

How to Contribute

  1. Open Issues: Found a bug or have a feature suggestion? Open an issue to describe what you'd like to see changed.

  2. Pull Requests: We welcome pull requests! If you'd like to contribute code:

    • Fork the repository
    • Create a new branch for your feature/fix
    • Submit a PR with a clear description of the changes and any related issues

  3. Feedback: Share your experience using the packages or suggest improvements.

All contributions, whether they're bug reports, feature requests, or code changes, help make this project better for everyone.

Please ensure your contributions adhere to our coding standards and include appropriate tests where applicable.