Introduction
A guillotina application to automatically generate swagger interfaces for APIs defined with guillotina.
Configuration
Available config.json options:
{
"swagger": {
"authentication_allowed": false,
"base_configuration": {
"swagger": "2.0",
"info": {
"version": "",
"title": "Guillotina",
"description": "The REST Resource API"
},
"host": "",
"basePath": "",
"schemes": [],
"produces": [
"application/json"
],
"consumes": [
"application/json"
],
"paths": {},
"definitions": {}
},
"index_html": null
}
}
Viewing swagger for resource
Append @docs onto any url: http://localhost:8080/@docs.
Generating swagger docs
guillotina_swagger reads service configuration.
You can provide additional swagger configuration hints by providing a swagger configuration with any of the following options:
ignore: to prevent swagger from aggregating it
additional_paths: provide a list of additional paths this configuration is used for(think routing here)
display_permission: if you do not want to show permission setting, set this to false
tags: what tags to use for it
1.0.14 (2019-06-18)
restrict g compat
1.0.13 (2018-09-26)
Only provide version if not set [vangheem]
1.0.12 (2018-09-20)
Be able to customize swagger index.html file [vangheem]
1.0.11 (2018-09-14)
bump
1.0.10 (2018-09-13)
More docs and support for customizing more parts of generated swagger definition. [vangheem]
1.0.8 (2017-06-19)
Add permission to documentation [vangheem]
1.0.7 (2017-06-18)
Tweak UI [vangheem]
1.0.6 (2017-06-18)
Automatically detect auth tokens and be able to provide own authorization header [vangheem]
1.0.5 (2017-06-13)
Also pull basePath for swagger from vhm if provided [vangheem]
1.0.4 (2017-06-13)
Use vhm for host setting on swagger [vangheem]
1.0.3 (2017-06-13)
Pay attention to vhm
1.0.2 (2017-06-12)
be able to provide custom base_url for swagger [vangheem]
1.0.1 (2017-06-07)
Fix getting path of resource
1.0.0 (2017-04-04)
initial release
Metadata
Release files for guillotina-swagger 1.0.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| guillotina_swagger-1.0.14.tar.gz | 1.0 MB | Without provenance | Details for guillotina_swagger-1.0.14.tar.gz |
Release files / guillotina_swagger-1.0.14.tar.gz
| Download URL | guillotina_swagger-1.0.14.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5aa822c7fe17737b2bdf0c3a209f6bf06369421e938b60c41c82de2082fc15bb
|
|
BLAKE2b-256 checksum How to use checksums |
5f90e37b47c9c9b2add3134864cd36cc824149e39f30839796b1e1e699edb770
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.6
|
Security for guillotina-swagger 1.0.14
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.