v0.12

Changelog:

• Fix a crash in debug mode when trying to dump undefined values.
• When using Mojo::UserAgent and in debug mode, print out the real reason of failure when a
  connection fails due to a proxy error. Before, only an opaque "Proxy connection error" would
  have been returned. See issue #29.

v0.11

Changelog:

• Replace deprecated calls to Mojo::Transaction::success with Mojo::Transaction::error (see issue #28). Thanks @huckeduster!

v0.10

Changelog:

• Wrap calls to JSON::MaybeXS::encode_json() with parentheses. This fixes recent test failures. Thanks Flavio (@polettix)!

v0.09

Changelog:

• Fix error messages containing "at" being incorrectly parsed by parse_error. See issue #19.
  Thanks Thomas!

v0.08

Changelog:

• Handle plain text error messages returned by old versions of Mojolicious. See issue #16.
• Add a note in the documentation about how important is to reuse objects and the undefined behavior that happens with asynchronous requests when that rule is not honoured. See issue #13.

v0.07

Changelog:

• Don't encode to UTF-8 when JSON::MaybeXS takes care of it.

v0.06

Changelog:

• Fix a critical encoding issue involving LWP, file uploads and UTF-8 fields.

v0.05

Changelog:

• Fix compatibility with older Perls.
• Improve debugging output.

v0.04

Changelog:

• Major change to how requests are handled. Every request is now sent using application/json by default, except when uploading, where multipart/form-data is used instead.

  This has the benefit of allowing the usage of complex objects with zero effort. It should not be a breaking change (except if dealing with the internals of this module).

• Implement parse_error. This new method allows to parse errors and obtain information about them, such as their source or code. Please see the updated documentation.

• Asynchronous callbacks are no more mandatory when async mode is enabled. When the callback is missing, requests are simply executed synchronously.

v0.03 - The spookiest release ever!

Happy Halloween!

Changelog:

• Add new debugging mode, enabled by setting the TELEGRAM_BOTAPI_DEBUG environment variable
  to a true value.
• api_request now dies when, in the response, ok is missing or set to a false value.
  This means that undef can no longer be returned.
  Consequently, error messages returned from Telegram - when available - are now shown when
  dying (instead of showing just the HTTP response code).
• Several improvements to the documentation and the code.