When the client requests a model with client-side layout, but no server-side layout, the server responds with a RequestBoundsAction. The client never replies to that second request, but generates a SetBoundsAction locally:
This is a bit strange. The server should send a SetModelAction instead, and the client should take care of the RequestBounds / ComputedBounds cycle locally.
When the client requests a model with client-side layout, but no server-side layout, the server responds with a RequestBoundsAction. The client never replies to that second request, but generates a SetBoundsAction locally:
https://github.com/eclipse/sprotty/blob/d039fe732581f7626da34852160b038f06f21b38/src/model-source/diagram-server.ts#L184-L198
This is a bit strange. The server should send a SetModelAction instead, and the client should take care of the RequestBounds / ComputedBounds cycle locally.