refactor: drop update info handling - #2644
Merged
Merged
Conversation
winged
force-pushed
the
drop_update_info
branch
from
August 25, 2026 13:54
0b0bb17 to
c46efc8
Compare
The previous version of the recalculation code needed the update info for deciding whether to update some table rows or not. This is now entirely obsolete and we don't need that information anymore. So we don't pass it along, and don't even collect it anymore.
winged
force-pushed
the
drop_update_info
branch
from
August 25, 2026 13:54
c46efc8 to
9f40280
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The previous version of the recalculation code needed the update info for deciding whether to update some table rows or not. This is now entirely obsolete and we don't need that information anymore. So we don't pass it along, and don't even collect it anymore.