You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all methods mutating the entity path filter in a ViewContents write the mutated filter to the blueprint store but leaves the deserialised version unchanged. This means that all mutations are lost except the last one within a frame, which is a major foot-gun. We should fix this API such as to allow arbitrary number of mutations during a frame (while retaining interior mutability for the ViewportBlueprint structure and friends).
The text was updated successfully, but these errors were encountered:
### Related
* Related to #8518
* Related to #8431
### What
Fix a bug in #8431 where multi-entity drag-and-drop would only add a
single entity due to a foot-gun in our entity path filter mutation API
(see #8518 for more). Also add a new checklist.
Currently, all methods mutating the entity path filter in a
ViewContents
write the mutated filter to the blueprint store but leaves the deserialised version unchanged. This means that all mutations are lost except the last one within a frame, which is a major foot-gun. We should fix this API such as to allow arbitrary number of mutations during a frame (while retaining interior mutability for theViewportBlueprint
structure and friends).The text was updated successfully, but these errors were encountered: