github/penpot
1
0
Fork 0
mirror of https://github.com/penpot/penpot.git synced 2026-10-29 14:00:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

📚 Describe the listing summary cache

Browse Source
This commit is contained in:
Álvaro Tejero Cantero 2026-08-13 20:22:13 +02:00
parent a844752c47
commit f39905455e
No known key found for this signature in database
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/technical-guide/developer/branching.md
View File

@ -242,6 +242,16 @@ there is a two-level gate (`branch-diff-counts`):
branch: count errors degrade to zeros with a warning (the merge itself
still refuses loudly).
The computed `[ahead behind conflicts]` summary is cached in-memory
(`files-branch::branch-summary-cache`) keyed by
`(base-snapshot-id, source-revn, branch-revn)`. The key names exactly the
inputs the computation reads, so a stale entry cannot exist and the cache
needs no invalidation logic: a cache miss is the cold path, and a repeated
listing with no intervening save performs no comparison work. The cache
bounds memory (`max-size`, `keepalive`) and never decides correctness, and
a failed computation is not stored, so a broken branch keeps degrading to
zeros with a warning on every listing.
## The three-way diff engine
`app.common.files.branch-merge` is the heart of the feature. It is a pure,