Constraints in state objects #359
Labels
2.1.0-CSD.1
Will be fixed in SARIF v2.1.0 CSD.1.
enhancement
impact-non-breaking-change
merged
Changes merged into provisional draft.
resolved-fixed
@kupsch made this suggestion in a comment on #168:
For many of the tools that I have seen that include flows or traversals, when explaining a flow or graph traversal state, they specify the value of an expression as a literal value (expressible in this current design), or as a constraint on the value (currently not not expressible). Such as
This state constraint information that many tools report, could incorporate this without changing the schema by describing that a magic string value such as "{expr}" is used to represent a constraint expression. If "{expr}" exists in the value then it is a constraint (the value may substitute the actual expression for {expr}. If "{expr}" does not exist in the value then this is an equality constraint equivalent to "{expr} == VALUE" where VALUE is the value of the JSON property.
The above constraints would then become a state object of
For viewer just displaying the values above would probably be deciphered with the correct meaning by most developers, and advanced viewers could do more to indicate a general constraint instead of just equality.
The text was updated successfully, but these errors were encountered: