I'm trying to invoke a worker from our serverless functions and using reqwest via REST with typed json is a bit cumbersome. I looked into using your generated golem-client but due to its dependency on golem-common it pulls in a lot of crates that don't compile on wasm32-wasip2 that maybe don't need to be there for an API client to work like wasmtime or cranelift-codegen.
I may also just have misunderstood what golem-clients purpose is.
That's true, we should introduce features into golem-common so those parts become optional. The generated client code only depends on this crate to share some of the model types instead of "regenerating" them.
Hi,
I'm trying to invoke a worker from our serverless functions and using reqwest via REST with typed json is a bit cumbersome. I looked into using your generated
golem-client
but due to its dependency ongolem-common
it pulls in a lot of crates that don't compile onwasm32-wasip2
that maybe don't need to be there for an API client to work likewasmtime
orcranelift-codegen
. I may also just have misunderstood whatgolem-client
s purpose is.