Having two separate servers and communication methods resulted in additional maintenance & the need to convert often between backend & frontend data types.
By moving the backend communication off of gRPC and to just use websockets it both gives more control & allows for simplification of the implementation.
New implementation automatically handles reconnect logic
Implements an api layer
Migrates examples to the api layer
Implements a proc macro to make command handling easier
Implements unit tests for the api layer (90+% coverage)
Implements integration tests for the proc macro (90+% coverage)
**Rationale:**
Having two separate servers and communication methods resulted in additional maintenance & the need to convert often between backend & frontend data types.
By moving the backend communication off of gRPC and to just use websockets it both gives more control & allows for simplification of the implementation.
https://gitea.sergeysav.com/sergeysav/telemetry_visualization/issues/8
**Changes:**
- Replaces gRPC backend.
- New implementation automatically handles reconnect logic
- Implements an api layer
- Migrates examples to the api layer
- Implements a proc macro to make command handling easier
- Implements unit tests for the api layer (90+% coverage)
- Implements integration tests for the proc macro (90+% coverage)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Rationale:
Having two separate servers and communication methods resulted in additional maintenance & the need to convert often between backend & frontend data types.
By moving the backend communication off of gRPC and to just use websockets it both gives more control & allows for simplification of the implementation.
#8
Changes: