All Versions
62
Latest Version
Avg Release Cycle
61 days
Latest Release
402 days ago

Changelog History
Page 5

  • v0.5.1 Changes

    April 10, 2018

    โž• Added

    • Decorator uplink.returns.model for specifying custom return type without
      indicating a specific data deserialization format.

    ๐Ÿ›  Fixed

    • Have uplink.Body decorator accept any type, not just mappings.
    • Reintroduce the uplink.returns decorator.
  • v0.5.1._ Changes

    โž• Added

    • Decorator uplink.returns.model for specifying custom return type without indicating a specific data deserialization format.

    ๐Ÿ›  Fixed

    • Have uplink.Body decorator accept any type, not just mappings.
    • Reintroduce the uplink.returns decorator.
  • v0.5.5_ Changes

    ๐Ÿ›  Fixed

    • Issue with sending JSON list Body using @json annotation.
  • v0.5.4_ Changes

    ๐Ÿ›  Fixed

    • When using uplink.AiohttpClient with aiohttp>=3.0, the underlying aiohttp.ClientSession would remain open on program exit.
  • v0.5.3_ Changes

    ๐Ÿ›  Fixed

    • Issue where adding two or more response handlers (i.e., functions decorated with uplink.response_handler) to a method caused a TypeError.
  • v0.5.2_ Changes

    ๐Ÿ›  Fixed

    • Applying returns.json decorator without arguments should produce JSON responses when the decorated method is lacking a return value annotation.
  • v0.5.1_ Changes

    โž• Added

    • Decorator uplink.returns.model for specifying custom return type without indicating a specific data deserialization format.

    ๐Ÿ›  Fixed

    • Have uplink.Body decorator accept any type, not just mappings.
    • Reintroduce the uplink.returns decorator.
  • v0.5.0_ Changes

    โž• Added

    • Decorators for convenient registration of custom serialization. (uplink.dumps) and deserialization (uplink.loads) strategies.
    • ๐Ÿ‘Œ Support for setting nested JSON fields with uplink.Field and uplink.json.
    • Optional args parameter to HTTP method decorators (e.g., uplink.get) for another Python 2.7-compatible alternative to annotating consumer method arguments with function annotations.
    • Decorator uplink.returns.json for converting HTTP response bodies into JSON objects or custom Python objects.
    • ๐Ÿ‘Œ Support for converting collections (e.g., converting a response body into a list of users).

    ๐Ÿ”„ Changed

    • Leveraging built-in converters (such as uplink.converters.MarshmallowConverter) no longer requires providing the converter when instantiating an uplink.Consumer subclass, as these converters are now implicitly included.

    ๐Ÿ›  Fixed

    • ๐Ÿ– uplink.response_handler and uplink.error_handler properly adopts the name and docstring of the wrapped function.
  • v0.5.0._ Changes

    โž• Added

    • Decorators for convenient registration of custom serialization. (uplink.dumps) and deserialization (uplink.loads) strategies.
    • ๐Ÿ‘Œ Support for setting nested JSON fields with uplink.Field and uplink.json.
    • Optional args parameter to HTTP method decorators (e.g., uplink.get) for another Python 2.7-compatible alternative to annotating consumer method arguments with function annotations.
    • Decorator uplink.returns.json for converting HTTP response bodies into JSON objects or custom Python objects.
    • ๐Ÿ‘Œ Support for converting collections (e.g., converting a response body into a list of users).

    ๐Ÿ”„ Changed

    • Leveraging built-in converters (such as uplink.converters.MarshmallowConverter) no longer requires providing the converter when instantiating an uplink.Consumer subclass, as these converters are now implicitly included.

    ๐Ÿ›  Fixed

    • ๐Ÿ– uplink.response_handler and uplink.error_handler properly adopts the name and docstring of the wrapped function.
  • v0.4.1._ Changes

    ๐Ÿ›  Fixed

    • Enforce method-level decorators override class-level decorators when they conflict.