Connexion

Latest version: v3.1.0

Safety actively analyzes 679296 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 24

2.1.0

Not secure
- Proper debug logs for aiohttp's StreamResponse (787)
- Fix cli --stub (800)
- Fix handling additionalProperties in body (789)
- Change can_read_body to body_exists in AioHttpApi.get_request (738)
- Removed duplicated calls of get_response method of the Api classes (809)
- Fix up array style defaults (803)

2.0.2

Not secure
- Enforce that spec has string keys (JSON does not support integer keys) (763)
- Add connexion.operation dummy module for backwards compatability (758)
- Only pass body on PATCH/POST/PUT request (761)
- Add support for JWT authentication (732)
- Don't let openapi_spec_validator tamper raw spec (762)
- Simplify Operation class construction (726)

2.0.1

Not secure
- Pass files to handler if filename in arguments _or_ has_kwargs (753)
- Handle TypeValidationError in form-data (749)
- Get rid of deprecation warning when using `connexion run ...` (745)

2.0

As 2.0 is a major version bump, you can expect some breaking changes from Connexion 1.5.3.

- You can now use openapi 3 specifications
- Swagger UI is now optional, and can be installed with `pip install connexion[swagger-ui]`
- App and Api options must be provided through the "options" argument (``old_style_options`` have been removed).
- You must specify a form content-type in 'consumes' in order to consume form data.
- The `Operation` interface has been formalized in the `AbstractOperation` class.
- The `Operation` class has been renamed to `Swagger2Operation`.
- Array parameter deserialization now follows the Swagger 2.0 spec more closely.
In situations when a query parameter is passed multiple times, and the collectionFormat is either csv or pipes, the right-most value will be used.
For example, `?q=1,2,3&q=4,5,6` will result in `q = [4, 5, 6]`.
The old behavior is available by setting the collectionFormat to `multi`, or by importing `decorators.uri_parsing.AlwaysMultiURIParser` and passing `parser_class=AlwaysMultiURIParser` to your Api.
- The spec validator library has changed from `swagger-spec-validator` to `openapi-spec-validator`.
- Errors that previously raised `SwaggerValidationError` now raise the `InvalidSpecification` exception.
All spec validation errors should be wrapped with `InvalidSpecification`.
- Support for nullable/x-nullable, readOnly and writeOnly/x-writeOnly has been added to the standard json schema validator.
- Custom validators can now be specified on api level (instead of app level).
- Added support for basic authentication and apikey authentication
- If unsupported security requirements are defined or ``x-tokenInfoFunc``/``x-tokenInfoUrl`` is missing, connexion now denies requests instead of allowing access without security-check.
- Accessing ``connexion.request.user`` / ``flask.request.user`` is no longer supported, use ``connexion.context['user']`` instead

2.0.0

Not secure

1.5.3

Not secure
- Fix error codes for bad Content-Types in body validator. (629)
- Add validator kind to error logs extra in validators (671)
- Improve metrics reporting (672)
- Improve coroutine detection (600)
- Add x-nullable support for body validators (642)

Page 7 of 24

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.