-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Composition is not-re-evaluated when node is expanded in the tree #6391
Labels
Milestone
Comments
15 tasks
ozyx
added a commit
that referenced
this issue
Mar 15, 2023
- On treeItem open, gets the latest composition from persistence - Composition was being refreshed, but only within the same instance (mutables)
15 tasks
Testing Instructions
|
ozyx
added a commit
that referenced
this issue
Mar 15, 2023
…6437) * fix(#6391): refresh composition on treeItem open - On treeItem open, gets the latest composition from persistence - Composition was being refreshed, but only within the same instance (mutables) * test: regression tests for localStorage and couch --------- Co-authored-by: Scott Bell <[email protected]>
Verified Fixed - Testathon 3/16 on couch, AND local storage |
verified |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When a child is added to a parent object in another tab (or by another user) it does not appear in the tree even after collapsing and expanding the parent node. It appears that the composition is cached in the tree and is not re-evaluated every time the parent node is expanded.
Expected vs Current Behavior
The new child should appear after collapsing and expanding the parent node.
Steps to Reproduce
Environment
Impact Check List
Additional Information
The text was updated successfully, but these errors were encountered: