Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds SARIF traces support to SAPP #93
Adds SARIF traces support to SAPP #93
Changes from 1 commit
fc5695c
d8f1b06
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we move all the logic regarding sarif into
sarif.py
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which part exactly you'd like to move to
sarif.py
. Theto_sarif
function body just find the traces and calls_sarif_codeflow_location_from_trace_tuple
. I don't want to move the latter tosarif.py
because it is specific to traces. It is a private function that takes a trace_frame, tool and return the sarif codeflows object.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well IMO anything related to sarif should go into
sarif.py
. If we start putting function from every format intotrace.py
it will get overwhelming soon.trace.py
should provide a clean API that allows any formatter to get the data and do it's formatting.From what I see, everything we use in the
sarif
functions is public? Tell me if I'm wrong.