Current cassette test data are defined as literal string of JSON data. This makes it relatively hard to parse and understand the result, requires manual reformat, and can introduce big diffs during PRs.
An alternative would be to register a serializer/deserializer, such as in the below references, such that JSON formatted content can be directly embedded in the cassettes YAML.
https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2945/files#diff-cb551087f8ae85df8f036c12505349a8151577dbdc1f3bbea6b19dd62293008c
Found from kevin1024/vcrpy#580
Originally posted by @fmigneault in #107 (comment)
Current cassette test data are defined as literal string of JSON data. This makes it relatively hard to parse and understand the result, requires manual reformat, and can introduce big diffs during PRs.
An alternative would be to register a serializer/deserializer, such as in the below references, such that JSON formatted content can be directly embedded in the cassettes YAML.
https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2945/files#diff-cb551087f8ae85df8f036c12505349a8151577dbdc1f3bbea6b19dd62293008c
Found from kevin1024/vcrpy#580
Originally posted by @fmigneault in #107 (comment)