-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Python: Autoformat everything using qlformat.
#3915
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
Python: Autoformat everything using qlformat.
#3915
Conversation
Will need subsequent PRs fixing up test failures (due to deprecated methods moving around), but other than that everything should be straight-forward.
RasmusWL
left a comment
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.
Looked over all non whitespace-only changes, and it looks good 👍
|
|
||
| // /** | ||
| // * Holds if taint propagates from `source` to `sink` in zero or more local | ||
| // * (intra-procedural) steps. | ||
| // */ | ||
| // predicate localTaint(DataFlow::Node source, DataFlow::Node sink) { localTaintStep*(source, sink) } | ||
|
|
||
| // // /** | ||
| // // * Holds if taint can flow from `e1` to `e2` in zero or more | ||
| // // * local (intra-procedural) steps. | ||
| // // */ | ||
| // // predicate localExprTaint(Expr e1, Expr e2) { | ||
| // // localTaint(DataFlow::exprNode(e1), DataFlow::exprNode(e2)) | ||
| // // } | ||
|
|
||
| // // /** A member (property or field) that is tainted if its containing object is tainted. */ | ||
| // // abstract class TaintedMember extends AssignableMember { } | ||
|
|
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.
:(
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, huh. I guess those empty lines really ought to have had empty comments as well.
#3443 revived. (There were too many merge errors to deal with otherwise.)
Will need subsequent PRs fixing up test failures (due to deprecated
methods moving around), but other than that everything should be
straight-forward.