bowline_client 1.0.0
“Runtime for Bowline generated Elixir clients”
DirectoryEntry property write API callReferences a public code-forge URL
SHA-256b0caf658abc9bc3abade9307397a037fa18cc10e6b6e353db2c400beae1b05be
MaleculeH₂(CmOs)
Evidence
3:8… procedure calls to a Bowline handler over HTTP and maps every outcome
4 to `{:ok, value}` or `{:error, %BowlineClient.Error{}}`.
5
6 Queries go out as `GET` with the input in the `input` query parameter;
7 mutations and sensitive queries go out as `POST` with a JSON body.
8 """
9
10 alias BowlineClient.Error
11 alias BowlineClient.SSE
12
13 @type method :: :get | :post
14 @type headers ::
15 %{optional(String.t()) => String.t …
25:35… %{}, req: nil
26
27 @doc """
28 Builds a transport for the API served at `base_url`.
29
30 Options: `:headers` as a map or a zero-arity function evaluate …
96:64… son"},
97 file: {content, filename: filename, content_type: "application/octet-stream"}
98 ]
99
⋯5 lines
1# bowline_client
2
3The Elixir client runtime for [Bowline](https://github.com/bowlinedev/bowline).
4
5Bowline turns your Go code into typed API clients. This package is what the generated `bowline.ex` uses to make calls.
6
7## Install
8
9```elixir
10def deps …
22:63… r Go code.
23
24Errors come back as `Bowline.Error` with the same codes the Go server uses. Queries are sent as `GET`, mutations as `POST`. Inputs are c …
No evidence locations were recorded for this file. Raw result