Uplink changelog

Changelog History

Page 4

• v0.5.3 Changes

  May 31, 2018

  🛠 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.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

  May 30, 2018

  🛠 Fixed

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

• 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

  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.

• « First
• ‹ Prev
• 1
• 2
• 3
• 4
• 5
• 6
• Next ›
• Last »