Releases · mulesoft-catalyst/error-handler-plugin

Updated to Mule LTS 4.4.0. Also small updates to Readme and previous error to be more flexible. by @titans-of-code in #27
Removed built-in getPreviousError dataweave function and provided example in customErrors.dwl and README. This is very situational and should be handled in custom errors.

Full Changelog: 6.1.0...6.2.0

Compatibility

Compatible with 6.x versions with the exception of the Use Previous Error field. If you didn't use the default value, you will need to change it.

The Use Previous Error field has an empty string as default now, so if you relied on the previous default, it will now not retrieve any previous error. It will not break if you were using default value.
The Use Previous Error field is a different type for better editing. However, it is now its own child tag in the XML and not an attribute on the parent tag. If you put in a specific value in this field in a previous version, you will need to take that and move to the new field. This is a breaking scenario as the old attribute will not compile in this version.

titans-of-code

Assets 2

21 Dec 18:03

sf-charles

Merge pull request #21 from titans-of-code/feature/customNode

Added feature to customize the error response field name

Assets 2

20 Dec 23:02

sf-charles

Requires minimum Mule version: 4.3.0
The XML component namespace changed due to internal requirements so previous versions of this should be deleted from an app before using this version.
The API response format has breaking changes. While the response format has changed from versions previous to 6.0.0, which breaks the API contract, you can create the same response format by transforming this module's response to the old format, if that is desired.

The XML component namespace changed to module-error-handler-plugin.
The error response was simplified to only contain the error information. The API metadata was removed and errorDetails was changed to error. The previous error response was highly opinionated; the new response is simple and flexible to different needs. The metadata can be added outside of this component if needed. The API metadata is recommended to be returned via headers and not in the response body.
There is no longer a global configuration.
The error response fields below were removed.
- correlationId
- timestamp
- apiName
- version
- success
The Use Previous Error feature now replaces the error message instead of added to an array of error messages that includes the current error.
The error, previously errorDetails, is now a single object and not an array. The message is a string but can be customized to an array or object.