fix: do not emit DecodingError when response is null #22
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
btrautmann
commented
Dec 23, 2025
| } on Exception catch (e) { | ||
| await _onEvent( | ||
| DecodingError( | ||
| request: responsePayload.dioResponse!.requestOptions, |
Contributor
Author
There was a problem hiding this comment.
This null check previously caused a NPE (seen when migrating the TT dart client to this version).
Contributor
Author
|
/no-platform |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
📰 Summary of changes
This PR protects against the case where we get a
DecodingErrorwhen there was no response, which previously caused a null pointer. I think this is actually a fair trade-off, since we can't fail to decode something if there was nothing to decode.🧪 Testing done
Added a test for the same.