Fix bug where nested "bytes" property fails with TypeError #9
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.
If you try to send an http body with a nested "bytes" property that is a number it currently fails to execute.
Example request:
Error:
The root of the problem is a combination of our
fromTypedData
andconvertKeysToCamelCase
methods. I think both have some fundamental issues, but I'm wary of refactoring because it might break people relying on the existing behavior. For now, I think it's good enough for us to catch any error and use the original value. I will save bigger refactors for the new programming model.Fixes Azure/azure-functions-nodejs-worker#607