A lot of our examples of working with coverage are driven by CSV data, where coverage is stored as a JSON string. When working with other data formats (e.g., raw JSON) it is very easy to end up with a pandas DataFrame that stores a JSON object rather than a JSON string.
Since both are JSON, we should be permissive and accept both.
Request attributes
[ ] Would this be a refactor of existing code?
[ ] Does this proposal require new package dependencies?
[ ] Would this change break backwards compatibility?
Related issues
No response
Solution description
Check whether a given coverage entry is a string or an object, and handle it accordingly.
Feature/behavior summary
A lot of our examples of working with coverage are driven by CSV data, where coverage is stored as a JSON string. When working with other data formats (e.g., raw JSON) it is very easy to end up with a pandas
DataFramethat stores a JSON object rather than a JSON string.Since both are JSON, we should be permissive and accept both.
Request attributes
Related issues
No response
Solution description
Check whether a given coverage entry is a string or an object, and handle it accordingly.
Additional notes
No response