Fix encoder instanceof issue with Encoder #685
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.
@bfdill was having this issue where KafkaJS was failing to encode requests because
Encoder.writeEncoder
was throwing, because the value was not an instanceofEncoder
, even though we could clearly see that it was in fact an encoder. I don't have an explanation for this, but we have seen issues with instanceof before. I'm guessing that his project was doing something strange at build time, since it was a Typescript project (maybe he's accidentally transpilingnode_modules
).I thought about adding a
name
property to every instance of Encoder, but it feels a bit ugly, so I decided to go for an approach where we instead just check that the value is "Encoder-like", i.e. has abuffer
property with a Buffer inside it, since that's what we actually care about. Anyway the encoder is only an internal class, so it's mostly there to prevent us from shooting ourselves in the foot.