Create exception formatters for different exceptions #4378
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit changes the ExceptionFormatterResolver to return a new instance
of the now generic ExceptionFormatter for the type of exception.
This fixes a bug where an ExceptionFormatter of type IJsonFormatter
is returned for derived exception types, resulting in an InvalidCastException
at runtime.
Formatter instances created are cached in ElasticsearchNetFormatterResolver
for the type T, so will be reused once created.
Fixes #4294