harmony-development / harmony_rust_sdk Goto Github PK

For some weird reason, protoc on windows builds complain that a path is missing, but the path is actually there.

Ideally there should be two seperate clients: one "stateless" and one "stateful", stateful one basically being a batteries included higher level API while the stateless one is for people who don't need the full stateful client (or they just want more flexibility).

This needs legato and postgresql running in CI.

This will allow us to know if a method requires auth etc. It is blocked by tokio-rs/prost#317 and tokio-rs/prost#256.

In the meantime we should at least document these.

https://github.com/harmony-development/protocol/tree/main/name-resolution

This is blocked by tonic.

It's probably best to seperate the stuff into seperate crates. Probably:

• harmony_api: holds generated api code (control server / client code generation via a feature)
• harmony_api_macros: macros we'll use in api crates
• harmony_client_api: client api methods, client: &Client should be made generic using something like AsMut<...Service> instead
• harmony_federation_api: same as above but for server
• harmony_client_stateless: stateless client #3
• harmony_client_stateful: stateful client #3

and a harmony crate which re-exports these controlled with feature gates. Pretty much like ruma structure.

hyperium/tonic#515

• Message log example
• Echo bot example

https://harmonyapp.io/harmony_rust_sdk/harmony_rust_sdk/client/api/chat/message/trait.SendMessageSelfBuilder.html genereted doc has #name instead of the actual name. Fix this like we do with generated method comments, ie. do:

let doc_msg = format!("Builder trait for {}.", name);
// ...
quote! {
  #[doc = #doc_msg]
  // ...
}
...

instead of:

quote! {
  /// Builder trait for #name.
  // ...
}