The httpResponseSerializer
needs to find a serializer for a type
by searching all the types
#544
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.
What does this implement/fix? Explain your changes.
And all the
opts.serializers
too.Array.prototype.find
short circuits on truthy return values of its callback, which means that we only would've ever traversed the array for the first element oftypes
sinceopts.serializers.map
just returns an array of booleans right?Fix this typo and add a test to cover my use case of wanting to fall back to a default if no preferred serializer is found.
Does this close any currently open issues?
Nothing that I could find from my quick searching. I just needed this for myself right now.
Any relevant logs, error output, etc?
N/A
Any other comments?
None.
Where has this been tested?
Node.js Versions: 12
Middy Versions: 1
AWS SDK Versions: N/A
Todo list