Skip to content
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

WIP: BUGFIX: Flush content cache on discard #5155

Closed
wants to merge 2 commits into from

Conversation

grebaldi
Copy link
Contributor

fixes: #5150

WIP.

@github-actions github-actions bot added the 9.0 label Jun 21, 2024
The test scenario consists of a document with a main content collection
that initially contains two simple text content nodes.

During the scenario, we switch to a user workspace and insert a third
text node between the two initial nodes. The test then verifies, that
fusion renders all three text nodes in order.

Afterwards we discard the change we just made and check whether fusion
now stops rendering the discarded node. Confirming #5150, with this
commit, said verification fails.
This is achieved via a catch up hook for the workspace projection that
utilized info from the PendingChangesProjection to figure out which
nodes need to be considered for cache invalidation.
@dlubitz
Copy link
Contributor

dlubitz commented Aug 31, 2024

As this is fixed now properly, I close this one.

@dlubitz dlubitz closed this Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: Discarded node remains in cache if UI was reloaded between creation and discard
2 participants