-
Notifications
You must be signed in to change notification settings - Fork 668
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
Exclude placeholder #8836
Exclude placeholder #8836
Conversation
6036cb8
to
8a23229
Compare
4b5c249
to
f00c68b
Compare
d3434e9
to
f4014f3
Compare
if (item.folder() != f) { | ||
return false; | ||
} | ||
if (item.direction() == SyncFileItem::None) { |
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.
Might be easier to
return item.folder() == f && item.direction() != SyncFileItem::None;
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.
As we still have a TODO here I'd like to keep it.
(Currently we get one warning per sync run..., without skipping them the issues will get removed after the discovery which doesn't make much sense)
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.
For what it is worth, I love the verbose version without the &&
because I think it is easier to read and understand.
Prevent duplicates and guarantee sorting
f4014f3
to
95000a0
Compare
95000a0
to
e3f2c81
Compare
Kudos, SonarCloud Quality Gate passed! |
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.
LGTM
if (item.folder() != f) { | ||
return false; | ||
} | ||
if (item.direction() == SyncFileItem::None) { |
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.
For what it is worth, I love the verbose version without the &&
because I think it is easier to read and understand.
Confirmed fixed in 2.9.0-beta3 The client logs: |
No description provided.