|
Add codeflow.state to capture initial execution state for things like static variables?
Shall the design change be approved, and shall the resulting change draft be approved?
The change draft is referenced in this ballot.
The change draft is for the following issue.
https://github.com/oasis-tcs/sarif-spec/issues/168
The provisional draft with the changes from all ballots merged is here:
https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/ProvisionalDrafts/sarif-v2.0-csd02-provisional.docx
-----
E-BALLOT PROPOSAL:
In the codeFlow object:
Add property immutableState of type object with string-valued properties, to hold information like HTTP headers and forms data. That was the initial motivation for this issue.
Add property initialState of type object with string-valued properties (parallel to the existing property graphTraversal.initialState).
In the graphTraversal object:
Add property immutableState of type object with string-valued properties (parallel to the new property codeFlow.immutableState).
In the spec, clarify that threadFlowLocation.state and edgeTraversal.finalState must mention every relevant state variable, even those unchanged since the previous step, because otherwise, if a state variable was present at step n but missing at step n + 1, you couldn't tell if it still existed but its value was unchanged, or if it had gone out of scope.
|
