Description

How can I use socket.io instead of the plain websocket integration? I guess this is more a question belonging to starlette.

Currently migrating from a flask application using flask-socketio / python-socketio

Any hint is appreciated. Thx.

Description

The issue #1210 made me think it would be great to document request context management when using aiohttp server. At least inform that the given example in the doc does not work for aiohttp server.

Attempting to return the following data structure to the user and document properly in swagger:

{ 'dynamic_key_1': ['string1', 'string2'], 'dynamic_key_2': ['string3]', ... }

i.e. a dictionary with dynamic keys, where values are a list of strings.

Using the example from here can get simple dynamic

Copied from #103

I've resolved the issue of authentication using the next code:
swagger_template = { ..., 'securityDefinitions': { 'basicAuth': { 'type': 'basic' } }, ... }
app = Flask(__name__)
Swagger(app, config=config[config_name].swagger_config, template=swagger_template)

![image](https://use

I'm new to rest_framework but I'm using drf in combination with redoc and this library and it seems to work fantastic.

I was wondering how can I generate custom sections of the documentation for objects that are commonly reused across all API calls. For example, I have a token object that is query/post parameter so I would like this to be explained topic in its own section.

With the help of

$ curl 'http://127.0.0.1:5000/auth/oauth2/token?grant_type=client_credentials' --user 'documentation:KQ()SWK)SQK)QWSKQW(SKQ)S(QWSQW(SJ*HQ&HQW*SQ*^SSQWSGQSG'
{"access_token": "lYoijoYaTgXZi1bLQTs4PuItKsNHNY", "token_type": "Bearer", "expires_in": 3600, "scope": "users:write teams:write auth:write users:read auth:read teams:read"}

Grab the above access_token and access protected resour

When I run the sample from https://github.com/marshmallow-code/apispec/blob/dev/docs/quickstart.rst

the expected output

# {'components': {'parameters': {},
#                 'responses': {},
#                 'schemas': {'Gist': {'properties': {'id': {'format': 'int64',
#                                                            'type': 'integer'},
#                                

Please provide examples on connecting to DATBASE TABLES - New to Flask-RestX

Other codegen tools support circular references. See swagger-api/swagger-codegen#728.

I this this issue with the following yml:

  Node:
    description: Generic node.
    type: object
    properties:
      type:
        description: Type or label of the node.
        type: string
      properties:
        description: Node specific dictionary of key/value pairs

Based on #32 and discussion with @Hultner

• Have a smaller quickstart
• Link to docs in the top of the page (not only badge)
• Move documentation content to a separate document
• Share roadmap info
• Examples of errors that could be found
• Possible workflows for Schemathesis. As a part of a test suite, CI step, CLI, etc
• [Usage](https://github.com/untitaker/

Pyswagger appears to be expecting nested swagger.{json.yml} docs at each 'path' in the API tree for an API specified as a local files, (file://):

I have a swagger 1.2 doc, applications.json, handed to me from another team from which to develop a client.

(output truncated for brevity)

----> 3 api_applications = App.create('./applications.json')

~/.pyenv/versions/3.6.5/envs/3.6/lib

In YAML you can write strings without quotes. For some specific cases you are forced to use quotes, for example when you put digits, but you want them to be of type string.
But when you write schema and set type of variable to string - when you provide example you expect that it will also be of type string. But it's converted to the python as integer.

Expected Behaviour

Some schema in `req

Please describe the request object for the request_parameters_factory.create. Can't find it in source code.

Is it possible to validate a response data?

If the field 'username' is not filled in input an appropriate error message should be showned and listed under the 400 Response.

To Reproduce

Steps to reproduce the behavior:

1. Go to 'User-Register'
2. {
   "name": "testua",
   "username": "",
   "password": "testua123",
   "email": "voxij69223@mailop7.com",
   "terms_and_cond