Skip to content

Commit

Permalink
#179: Don't replace conversion.tool with conversion.driver
Browse files Browse the repository at this point in the history
conversion.tool is the conversion scenario analog of run.tool.
Both the direct production and the conversion scenarios are
accomplished by a tool that consists of a driver, and possibly
a set of auxiliary files including plugins and configuration files.
In the conversion scenario, configuration files are more likely
than plugins, but that’s neither here nor there.
  • Loading branch information
Larry Golding committed Feb 14, 2019
1 parent 2c0ac6a commit 9d460dd
Showing 1 changed file with 0 additions and 4 deletions.
4 changes: 0 additions & 4 deletions Documents/Schema changes between SARIF v1 and v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -1266,10 +1266,6 @@ _and_ [Issue #311](https://github.com/oasis-tcs/sarif-spec/issues/311): "Provide
- Add a property `notificationIndex` of type `integer`, `default: -1`. optional.
- Add a property `notificationExtensionIndex` of type `integer`, `default: -1`. optional.

In the `conversion` object:

- Rename the `tool` property to `driver`, and change its type from `tool` to `toolComponent`.

- [Issue #312](https://github.com/oasis-tcs/sarif-spec/issues/312): "Consider adding 'updated' baselineState"

In the `result` object:
Expand Down

0 comments on commit 9d460dd

Please sign in to comment.