Fix field name that the API actually returns #33
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.
When querying
/usage/failed
, this Python client looks for a key namedValidationFailedRecords
in the response object. But the API actually returns a key namedFailedRecords
:As a result,
client.get_failed_records()
was returning<FailedUsageResponse: 0 records>
when we definitely had some failed records. With the change in this PR, I now see<FailedUsageResponse: 1539 records>
, what I would expect.