Fix!: Remove JSON parsing error and update detailed report formatting #12
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.
What
json.loads
inextract_error_message
to avoidTypeError
when processing API responses already in dictionary format.--export_csv
argument for accessing error messages.Why
json.loads
on a dictionary object caused aTypeError
. This change ensures compatibility with API responses that are already deserialized into dictionaries.How
json.loads(result)
with direct usage of theresult
dictionary inextract_error_message
.print_report
to exclude the error message column and display a note about the--export_csv
option.Can this PR break any existing features. If yes, please list possible items. If no, please explain why.