[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes (NA)
[x] I translated all the newly inserted strings into German and English (NA)
Motivation and Context
Currently in Apollon, when a patch is imported (via .importPatch()), it will result in all elements of the diagram being re-rendered (re-constructed from scratch), lowering performance and stability.
Description
This PR introduces an option for patcher-reducer to accept custom merge functions for updating state (instead of the default naive solution of object assignment). It also adds a specific merge function for ModelState that merges two model states gracefully, maintaining instance references and diagram boundaries, and gracefully updating diagram metadata. As a result, the subsequent re-render of the diagram maintains all SVG elements and only updates / reconstructs what is necessary.
Build and run Apollon standalone. Share a diagram for collaboration, open in two separate browser instances.
Inspect an element of the diagram in one browser instance, change something in the diagram in the other browser instance. The element should remain the same except for change of ownership or when it is deleted. You can verify this by adding a custom HTML attribute (e.g. data-x="42") to the element, and verifying that it still exists after the clients sync on the changes.
Checklist
I added multiple screenshots/screencasts of my UI changes(NA)I translated all the newly inserted strings into German and English(NA)Motivation and Context
Currently in Apollon, when a patch is imported (via
.importPatch()), it will result in all elements of the diagram being re-rendered (re-constructed from scratch), lowering performance and stability.Description
This PR introduces an option for
patcher-reducerto accept custom merge functions for updating state (instead of the default naive solution of object assignment). It also adds a specific merge function forModelStatethat merges two model states gracefully, maintaining instance references and diagram boundaries, and gracefully updating diagram metadata. As a result, the subsequent re-render of the diagram maintains all SVG elements and only updates / reconstructs what is necessary.Steps for Testing
data-x="42") to the element, and verifying that it still exists after the clients sync on the changes.Test Coverage