-
Notifications
You must be signed in to change notification settings - Fork 289
refactor(common): LinkedChunk
can start by a gap
#4653
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
refactor(common): LinkedChunk
can start by a gap
#4653
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4653 +/- ##
==========================================
+ Coverage 85.68% 85.69% +0.01%
==========================================
Files 292 292
Lines 33570 33600 +30
==========================================
+ Hits 28763 28794 +31
+ Misses 4807 4806 -1 ☔ View full report in Codecov by Sentry. |
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.
Thanks! Glad to see this invariant go 🥳
I'm mostly curious to see the final form of the code, but my comments are all mostly cosmetic and the code LGTM so approving to not block merging of dependent PRs.
This patch removes the invariant stating that a `LinkedChunk` must start by a chunk of type items. This has never been really useful but it's now annoying to have this (with iterative loading of a `LinkedChunk` via the `EventCache`, it's now possible to get a gap as the first chunk). Let's remove this invariant.
This patch splits the `test_replace_at` test into 3 smaller tests.
This patch updates the `test_replace_item` test to ensure `Update::ReplaceItem` is correct.
This patch splits the `test_insert_items_at` test into 5 tests.
e29958f
to
74f927b
Compare
I've improved the comments a bit. I've also split the |
This patch removes the invariant stating that a
LinkedChunk
must start by a chunk of type items. This has never been really useful but it's now annoying to have this (with iterative loading of aLinkedChunk
via theEventCache
, it's now possible to get a gap as the first chunk). Let's remove this invariant.EventCache
storage #3280EventCache
lazy-loading #4632