-
Notifications
You must be signed in to change notification settings - Fork 10
Remove V2 finding compatibility for FixResult #1063
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
Conversation
| assert f.changeSets and f.changeSets[0].diff == v2changeset.diff | ||
| assert isinstance(f.finding, Finding) and f.changeSets[0].changes == [ | ||
| v2_finding_to_change[f.finding].to_common() | ||
| assert isinstance(f.finding, FindingV3) and f.changeSets[0].changes == [ |
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.
What is FindingV3?
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.
It's just an alias for the CodeTFv3 version of Finding
afd9a7f to
90d4d45
Compare
90d4d45 to
6589613
Compare
|



Instead explicitly convert V2 findings into V3 findings where necessary. This simplifies some assumptions for consumers of
FixResult