Version 0.4.0

Overview

• Added support to notify about unexpected errors
• Fixed possible naming clash for configuration method in controller
• Added a support to handle all errors that inherit from JsonapiErrorsHandler::Errors::StandardError - by default.

Version 0.3.0

• Improved code quality
• Hooked up reporting
• removed irb from the required file list
• added required ruby version
• upgraded dependencies

Version 0.2.0

This release contains a bug fix that makes the gem backward-incompatible in some cases.

**Description: **

ErrorSerializer returned

  {
    errors: [[...]] 
  ]

when called with an array of validation errors.

Now it matches the https://jsonapi.org specification for errors format.

Fix naming clash for rails applications

Rails applications have config method defined in controllers so our configuration overrode that which ended up with an error.

Add basic configuration and better handling for unmapped errors

• ee04b4f - Fix configuration and spec files
• 1877069 - Update README to include information about handling validation errors
• 2729bb4 - Fix rendering unhandled errors and instance errors

Fix custom details for errors

In this release, we fixed the issue with setting up custom error messages (error details for validation errors) as well as setting up the custom details.

Fix Mapping error

We had a bug in error mapper, and therefore mapping errors according to Readme did not work.

Fix validation error

The Jsonapi::Errors::StandardError had reversed dependency, which caused a bug that any updates to serializable_hash was ignored on rendering.

Now it's fixed.

Todo:

• cover errors code with tests to prevent situation like this in the future

Custom error logging

Version change log:

1. Added a custom logging mechanism
2. Improved documentation
3. Configured Rubocop and Codacy for high quality code.

[PATCH] require_dependency error

Changelog:

• #4 - ErrorMapper is now tested.
• #3 - require_dependency is not used so it's more integrated with Non-Rails applications