Using api-client for real client application about wire-server

[jschaul]

Hi @heroin-moose

We currently use the api-client (through the higher-level api-bot library) as part of our smoke tests. As such, it is unlikely to be removed in the future. Please note that it is not entirely complete and not our priority to keep up-to-date (Pull requests are always welcome if you find an API call which isn't implemented). Instead of using a git submodule, you could also refer to wire-server through your stack.yaml, e.g.

packages:
- '.'
- location:
    git: https://github.com/wireapp/wire-server.git
    commit: daa88e58e19f933143eeef386baa6e2bb8dadd7a
  subdirs:
  - libs/api-client
  - libs/api-bot
  extra-dep: true

Finally, for building a native Wire client, you may, in case you prefer another implementation language to Haskell, potentially also want to look at https://github.com/wireapp/coax (an incomplete Rust implementation - please note the warnings in the README)

[heroin-moose]

Instead of using a git submodule, you could also refer to wire-server through your stack.yaml

Yeah, already did it. Hail to the stack.

Finally, for building a native Wire client, you may, in case you prefer another implementation language to Haskell, potentially also want to look at https://github.com/wireapp/coax (an incomplete Rust implementation - please note the warnings in the README).

I'm not a big fan of Rust or GTK so my language of choice (for now) is Haskell. I'm trying to make my app more or less toolkit agnostic. Currently I read wire-server and coax in order to understand the protocol (both JSON and Protobuf), but a guide written by developers would be awesome (should we expect one?). I found Swagger.hs files that define some API endpoints, but I guess there's more to it. Also, there is no description (or I failed to find one) for the call sequences (things like "POST /login" -> "POST /access every 15 minutes" are pretty obvious, but other things may be not).

[jschaul]

but a guide written by developers would be awesome (should we expect one?). I found Swagger.hs files that define some API endpoints, but I guess there's more to it. Also, there is no description (or I failed to find one) for the call sequences (things like "POST /login" -> "POST /access every 15 minutes" are pretty obvious, but other things may be not).

We have some documentation for client developers regarding call sequences and semantics, which is currently not open-sourced. We plan to release some of that eventually. This issue would then be updated if/when that happens.

[heroin-moose]

It's nice to hear that, thanks.

[tiago-loureiro]

@heroin-moose Could you please close down this issue if you have no further questions on this topic?

[heroin-moose]

Sure thing.