|
External property file related renames?
EBALLOT PROPOSAL: rename the external property files object 'properties' member so that it does not collide with the general SARIF design standard of populating all object types with a property bag of that name. This allows the external property file to both have its own property bag (named 'properties') while also allowing it to externalize a run-level properties object (which we will not call 'externalizedProperties')
API IMPACT
In the externalPropertyFiles object:
Rename the properties property to externalizedProperties.
Restore the properties property, which now refers to the object level property bag, not to externalized content.
In the externalPropertyFiles object:
Rename the instanceGuid property to guid.
Rename the artifactLocationproperty to location
https://github.com/oasis-tcs/sarif-spec/issues/335
|
