feat!: Decode returns opaque event objects when a formatter is not available #58
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.
HttpBinding#decode_rack_envto return an opaque object if the format isn't recognizedHttpContentErrorclass and instead introducedUnsupportedFormatError, to keep error classes binding-agnostic.FormatSyntaxErrorto report parsing errors during decoding. These were previously reported as raw JSON errors. (The JSON errors are still set as thecause.)HttpBinding#encode_eventas a single entrypoint for encoding. Deprecatedencode_structured_content,encode_batched_content, andencode_binary_content.Signed-off-by: Daniel Azuma [email protected]