|
Provide mechanism for inlining externalized properties data into the root log?
EBALLOT PROPOSAL: provide a mechanism for inlining externalized property data at the log level. This facility allows for shared data between runs that is itself persisted to the log (e.g., common taxonomy metadata will be useful to store in this way).
API IMPACT:
Add sarifLog.inlineExternalPropertyFiles, an array of externalPropertyFile objects (already defined in the schema)
NOTES:
The run-level property run.externalPropertyFiles can specify the location of an inline external property file in two ways.
A uri property under run.externalPropertyFiles (for example, externalPropertyFiles/conversion/fileLocation/uri) can specify the sarif scheme and a JSON pointer (e.g., sarif://inlineExternalPropertyFiles/6)
An instanceGuid property under run.externalPropertyFiles (for example, externalPropertyFiles/conversion/instanceGuid) can match the instanceGuid property of one of the externalPropertyFile objects in sarifLog.inlineExternalPropertyFiles.
https://github.com/oasis-tcs/sarif-spec/issues/321
|
