Update cell on ResourceChanged - #1438
Draft
dbeuchler wants to merge 4 commits into
Draft
Conversation
dbeuchler
force-pushed
the
improve/update-cell-on-resource-change
branch
from
August 14, 2026 11:41
3c2cc2b to
1175971
Compare
dbeuchler
changed the title
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
1 participant
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.
based on #1437
There a hardcoded 5 seconds timer in FactoryMonitor server instead of pushing changes directly by ResourceChanged event. This PR added ResourceChanged-event in addition to hardcoded timer.
I also introduced an option to RaiseResourceChanged that the persistence should not be triggered. Its a separate event on Resource which must be merged on future with Changed.
Open Question: Is the timer removal an behavior change we cannot introduce in 10.x? Resources which do not raise the event were updated before. With listening on ResourceChanged it is necessary that RaiseResourceChanged is raised in the resources.
future