fix(parser): overload parse when using envelope #885
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.
Issue #, if available:
Description of changes:
When using parse function with an envelope, Mypy doesn't allow setting an explicit type as
parse
returns aModel
while an envelope parse could return various types ranging from List[Model], Dict[str, Model], List[Optional[Model], and this can grow over time as more event types are defined too.This PR uses type function overload to ensure
parse
continues to return aModel
when no envelope is used, and when an envelope is used it'll propagate a generic type allowing an explicit type to be set at runtime.Gotcha
If you don't set an explicit type when using
parse
with envelope, Mypy will detect asAny
since MyPy can't have a generic return type in this case.Example
This uses a sample valid SNS payload as per the issue with an empty payload and with non-empty payload.
Mypy output
Python type evaluation
Checklist
Breaking change checklist
RFC issue #:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.