Skip to content

Releases: spec-first/connexion

2.5.1

19 Dec 08:28
f31ac61
Compare
Choose a tag to compare
  • Require Python 3.6 for pip installation (#1108)

2.5.0

16 Dec 13:47
Compare
Choose a tag to compare
  • Drop Python 2.7 support, support Python 3.8
  • Convert responses to raise ProblemException (#955)
  • Add error path to schema validation
  • Do not sanitize body keys in OpenAPI 3 (#1008)
  • Date/time serialization (#851)
  • Forward options to AioHTTP app (#885)
  • Returning tuples supported in AioHTTP (#849)
  • Allow Swagger UI configuration options (#948)
  • Remove security parameter to pass query validation (#470)
  • Allow users to enable debug mode via environment variable

2.4.0

18 Oct 11:46
c8d8973
Compare
Choose a tag to compare
  • Handle deepObject and explode: true (#971)
  • Support jsonschema > 3.0.0 (#1050)
  • Drop Python 3.4 and 3.5. Add Python 3.8 (#1056)
  • Fix deprecated import (#1044)
  • Bump Flask version (#995)

2.3.0

14 Jun 08:02
2.3.0
Compare
Choose a tag to compare
  • AioHttpApi oauth middleware catches all OAuth problems (#830)
  • Serve YAML spec (#842)
  • Added MethodViewResolver (#847)
  • Fix swagger console backslash redirect for aiohttp (#843)
  • Fix uwsgi metric collection (#972)
  • Respond with problems by default in aiohttp (#952)

2.2.0

24 Dec 07:31
2.2.0
Compare
Choose a tag to compare
  • Fix case sensitive headers in aiohttp (#825)
  • Fix passing empty object body (#815)
  • Fix openapi3 path and query validation (#821)
  • Add path to API only for HTTP operations (#817)
  • Added OpenAPI 3 getting API Key from cookie support (#794)

2.1.0

11 Dec 08:31
2.1.0
Compare
Choose a tag to compare
  • 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

15 Nov 10:26
2.0.2
Compare
Choose a tag to compare
  • 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

07 Nov 08:00
2.0.1
Compare
Choose a tag to compare
  • 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.0

05 Nov 14:29
2.0.0
44ea933
Compare
Choose a tag to compare

Connexion 2.0 supports version 3.0.x of the OpenAPI Specification!
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

1.5.3

17 Sep 06:23
1.5.3
Compare
Choose a tag to compare
  • 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)