[LKasianAnsys]

Issue

Resolves #30

Context

In server mode, the client never received the cross-section plane state. The server recorded it, but nothing wrote it to the trame state, so it was not sent to the client over the websocket. The server now publishes the plane under a serer_cross_section_state key, the same way it publishes server_camera_state, and the client caches it as it caches the camera. CameraPublisher is widened and renamed ViewRecordPublisher, since it now publishes both. A snapshot that still fails is caught nad logged in the Dash component instead of being left uncaught.

Manual check: Start a Visor instance in SERVER mode with a dataset, open it with Dash, and generate a Dash snapshot. The data should be printed, and it should reflect the live viewer at the time it was generated.

Copilot summary

This pull request introduces support for synchronizing the cross-section plane state between the server and client, alongside the existing camera state, in the Ansys Visor application. The changes generalize the publisher interface and update both the backend and frontend to handle the new server_cross_section_state key. Additionally, the client tests are extended to cover the new plane synchronization logic.

Backend cross-section state synchronization:

• Generalized the publisher interface from CameraPublisher to ViewRecordPublisher, allowing the server to publish both camera and cross-section plane records to the frontend. (src/ansys/visor/viewer/renderer/server_renderer.py, src/ansys/visor/viewer/app/trame/server_state_publisher.py, src/ansys/visor/viewer/vtk/scene/server_scene.py, src/ansys/visor/viewer/app/visor_vtk_server.py) [1] [2] [3] [4] [5] [6] [7] [8] [9]

Frontend test and state handling improvements:

• Updated the frontend FakeState test helper and ServerRendererCache tests to handle multiple state keys, including server_cross_section_state, and added new tests for cross-section plane cache behavior. (src/ansys/visor/visor-client/src/jest-tests/ServerRendererCache.test.ts) [1] [2] [3] [4] [5] [6] [7]

Error handling and documentation:

• Improved error handling in the Visordash React component for snapshot failures and updated the prop documentation to clarify behavior when a snapshot fails. (src/ansys/visor/dash/src/lib/components/Visordash.react.js) [1] [2]

These changes collectively enable robust, bi-directional synchronization of both camera and cross-section plane states between the server and client, and ensure the frontend is properly tested for these scenarios.