-
Notifications
You must be signed in to change notification settings - Fork 266
MNTOR-4981: Apply the chainsaw #6149
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
manually_resolved: boolean; | ||
broker_status: DataBrokerRemovalStatus; | ||
data_broker: string; | ||
source: MoscaryData["ScanResult"]["source"]; |
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.
Do we need to run the schema change first before this?
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.
The migration to change the schema is part of this PR (and of the same commit that modifies knex-tables
, so that it's easy to find).
? adjustedScanData.scan.onerep_scan_status === "in_progress" | ||
: adjustedScanData.scan?.status === "in_progress") && | ||
props.scanCount === 1; | ||
adjustedScanData.scan?.onerep_scan_status === "in_progress"; |
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.
Do we no longer need props.scanCount === 1
?
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.
Oh wow, very good find! I must have missed the closing bracket for the ternary, and thought the &&
was part of the :
branch. This would've been annoying to debug later. Fixed in c2ee90f.
c2ee90f
to
ae94ba8
Compare
References:
Jira: MNTOR-4981