fix: Bring back refresh request after reroot#211
Merged
Conversation
Member
Author
|
We should merge feature/edit-mode into feat/skeleton-ux-improvement after this gets merged |
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
2 participants
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.
Closes https://metacell.atlassian.net/browse/NA-884
Brings back the old behaviour of: after reroot succeeds, it refetches the affected skeleton with current edition times and updates cached source state for the reroot path nodes. If refresh fails, it invalidates the local skeleton cache instead of keeping stale edit state.
This is needed because catmaid reroot edition time is stale. This can be reverted when MetaCell/CATMAID#3 gets merged into catmaid main repo (and published)