fix(microservices): handle creating error header from typical object #9101
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When an error is thrown by a Kafka message handler, the
ServerKafka
will attempt to add the error message to a header namedkafka_nest-err
.This logic assumes the error can be converted directly to a
Buffer
viaBuffer.from(err)
. This does not support Error objects (or typical NestRpcException
).Issue Number: N/A
What is the new behavior?
It now checks for a
message
property before attempting to convert the error value to a Buffer.Does this PR introduce a breaking change?
Other information