v0.0.2

Add deprecation notices in v1

v2.1.0

Use reflect to deduce the errortype dynamically

This is to fix when a custom error type (type SomeError error) would default to *error.errorString, while the value could hold a different implementation.
This will now be deduced correctly.

v2.0.1

Add RegisterDefaultHandler as a method on the ErrorRegistry and deprecate SetDefaultResponse along with its properties in favour of a default handler.

v2.0.0

Prerelease of interface improvements and addition of context

v0.0.1

• Removed unused generic from NewErrorResponse
• Move creation of errorString handler to NewErrorRegistry call

v0.0.0

Initial release