Added row body to response so it can be used in cases when json parsing fail or posibly in other circumstances. #256
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
Owner
|
Thank you! |
renetik
added a commit
to renetik/Networking
that referenced
this pull request
Nov 10, 2020
* 'master' of https://github.com/3lvis/Networking: Update Networking.podspec Update Networking.podspec Update deployment target Update Networking.podspec Remove crashing in purging (3lvis#261) Remove forced crash in cacheOrPurgeData Add sponsor message Create FUNDING.yml Update Networking.podspec Delete .swift-version Update Networking.podspec Rename NetworkingResult (3lvis#259) Fix CI (3lvis#258) . no message (3lvis#256) Update config.yml (3lvis#247) Update Package.swift (3lvis#257)
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.
Fixes #255
I would suggest instead fix json parsing so it is better suited of parsing of data returned from server as I pointed out in this bug report but I get over this problem by being able to access row body and parse it by myself.