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.
fix: Fix process-changes not deduplicating changes correctly #14025
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
fix: Fix process-changes not deduplicating changes correctly #14025
Changes from all commits
d712e52
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.
I've only skimmed the changes, but does this work for
[Create(f1), Delete(f1), Create(f2), Delete(f2)]
?And generally, I don't think
dedup_by
guarantees anything about the order of calls. Maybe we should "just" keep a map fromFileId
toChangeKind
, and go over the input once and update the map, without sorting it first? It might even be (asymptotically) faster. We only keep oneChangeKind
per file, except for the "can't really occur" cases.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 should work, because the flag is only
true
at this point if it was set totrue
during the last call to the closure (the beginning of the closure resets it tofalse
).I agree that the code is hard to follow though, and
dedup_by
is probably not helping with that.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.
But on my example, this results in
[Delete(f1)]
instead of[]
, which is probably not desirable.collapsed_create_delete
will only cause the lastDelete
to be dropped.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.
A simple map might be a better choice here indeed