Support nested heartbeat response status in 2xx range #1106
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.
The HTTP response needs 201 or 202 because some proxies or other network configurations always return 200 status even for failed requests that don't reach the WakaTime API. Because the WakaTime API never responds to POST heartbeats with 200 status, we want to treat 200 status as an error and save the heartbeats to the local offline db.
But for the nested JSON array in the response content we can accept any 2xx status code.