In the Query Service we'll have proto definitions that describes the Mapper RPC.
We should enable grpc-web (through a Go gRPC handler) in the Query Service so we can support connections from a browser to the Mapper RPC.
We should setup a CI workflow that will do a TS client (code) generation from Mapper RPC proto files and publish to NPM as a package.
This workflow should run whenever we make new release in the repo.
- It should first check if the proto files in the Query Service changed (git diff the dir by using an action)
- If there is a change then trigger the process of generating a TS client and publishing it to the NPM registry with the same release version.
In the Query Service we'll have proto definitions that describes the Mapper RPC.
We should enable grpc-web (through a Go gRPC handler) in the Query Service so we can support connections from a browser to the Mapper RPC.
We should setup a CI workflow that will do a TS client (code) generation from Mapper RPC proto files and publish to NPM as a package.
This workflow should run whenever we make new release in the repo.