package-analysis icon indicating copy to clipboard operation
package-analysis copied to clipboard

Save schema version with results.json data

Open maxfisher-g opened this issue 3 years ago • 1 comments

As our data format matures over time, having the schema version as part of the data makes it a lot easier to determine what to do when you're trying to read it. It's not essential to have a version field in the schema (e.g. the version could be part of the file path) but we should do something to explicitly persist the schema version that the data is saved with

maxfisher-g avatar Oct 18 '22 05:10 maxfisher-g

We should have a "boring" outer dict containing very basic metadata such as schema version, time that the data was generated, perhaps data that triggered the job. Inside the outer dict (i.e. as a key-value pair) we have the "real" results

maxfisher-g avatar Oct 18 '22 06:10 maxfisher-g

This is done for static analysis, will be done as part of a larger planned dynamic analysis schema change later on

maxfisher-g avatar Oct 16 '23 03:10 maxfisher-g