cargosense / absinthe_client Goto Github PK

Hey @benwilson512, it seems like you bumped the version to 0.1.1 but that version isn't on Hex. Would you mind releasing it there as well, please? Thank you!

• Setup local reference app using graphql-ws
• Implement a GraphqlWS adapter on top of Mint.WebSocket
• Tests
• Add absinthe_graphql_ws to the test endpoint
• Document async differences

Thanks a lot for absinthe_client. We've been waiting for it for a long time.
One of the main issue with consuming any graphql api(our or 3rd party) is it can change.
We can use different codegen libraries to ensure that the code that we are using is not out of date in js/ts world.
We have artem in elixir world.

Would a codegen be within the scope of this project ? If yes, it would be quality of life addition 😊.
This can be very handy tool when our whole ui is just live_view and have almost zero js/ts.

Thanks again for open-sourcing absinthe_client.

@mcrumm I copied the usage code from the README into an iex session and got the following error

** (FunctionClauseError) no function clause matching in URI.parse/1

    The following arguments were given to URI.parse/1:

        # 1
        [graphql: "query { character(id: 1) { name } }"]

    Attempted function clauses (showing 2 out of 2):

        def parse(%URI{} = uri)
        def parse(string) when is_binary(string)

    (elixir 1.13.4) lib/uri.ex:765: URI.parse/1
    (req 0.3.6) lib/req.ex:423: Req.post/2
    (req 0.3.6) lib/req.ex:328: Req.post!/2

I ran:

Mix.install([
  {:absinthe_client, "~> 0.1.0"}
])

Req.new(base_url: "https://rickandmortyapi.com")
|> AbsintheClient.attach()
|> Req.post!(graphql: "query { character(id: 1) { name } }").body

Any idea what I'm doing wrong? I see that the output from AbsintheClient.attach() has a call to URI.parse with an empty string:

%Req.Request{
  method: :get,
  url: URI.parse(""),
  headers: [],
  body: nil,
  options: %{base_url: "https://rickandmortyapi.com"},
  registered_options: #MapSet<[:unix_socket, :params, :path_params, :async,
   :cache_dir, :base_url, :raw, :connect_options, :json, :connect_params,
   :user_agent, :max_retries, :auth, :pool_timeout, :location_trusted, :finch,
   :plug, :output, :compress_body, :receive_timeout, :finch_request,
   :compressed, :max_redirects, :web_socket, :range, :cache, :extract, :form,
   :retry_log_level, :follow_redirects, :retry_delay, :graphql, :decode_body,
   :http_errors, :retry]>,
  halted: false,
  adapter: &Req.Steps.run_finch/1,
  request_steps: [
    graphql_run: #Function<0.34809413/1 in AbsintheClient."-fun.run/1-">,
    put_user_agent: &Req.Steps.put_user_agent/1,
    compressed: &Req.Steps.compressed/1,
    encode_body: &Req.Steps.encode_body/1,
    put_base_url: &Req.Steps.put_base_url/1,
    auth: &Req.Steps.auth/1,
    put_params: &Req.Steps.put_params/1,
    put_path_params: &Req.Steps.put_path_params/1,
    put_range: &Req.Steps.put_range/1,
    cache: &Req.Steps.cache/1,
    put_plug: &Req.Steps.put_plug/1,
    compress_body: &Req.Steps.compress_body/1
  ],
  response_steps: [
    retry: &Req.Steps.retry/1,
    follow_redirects: &Req.Steps.follow_redirects/1,
    decompress_body: &Req.Steps.decompress_body/1,
    decode_body: &Req.Steps.decode_body/1,
    handle_http_errors: &Req.Steps.handle_http_errors/1,
    output: &Req.Steps.output/1
  ],
  error_steps: [retry: &Req.Steps.retry/1],
  private: %{}
}

Specifically authorization from the :auth option if set.

Because the lock depends on swoosh 1.14.2 which depends on req ~> 0.4 or ~> 1.0, the lock requires req ~> 0.4 or ~> 1.0.
And because every version of absinthe_client depends on req ~> 0.3.0, the lock is incompatible with absinthe_client.
And because your app depends on the lock, no version of absinthe_client is allowed.
So, because your app depends on absinthe_client ~> 0.1.0, version solving failed.

Currently there doesn't seem like a great way to refresh auth credentials when the bearer token expires so the socket connection gets stuck in a 401/403 loop trying to reconnect once the token expires. Slipstream has an example of what something like this might look like: https://github.com/NFIBrokerage/slipstream/tree/main/examples/token_refresh

Since I am the one who submitted the recent change allowing AbsintheClient's req dependency to go to 0.5.x, I need to follow that up with a problem I discovered while using the latest version of AbsintheClient.

I initially updated AbsintheClient without changing my version of req, so the problem wasn't immediately apparent. Today when I tried to update req, I ran into some unexpected dialyzer errors that I narrowed down to the function that calls AbsintheClient.attach(). The error is Function some_func/0 has no local return for the calling function.

In order to narrow the scope of investigation, I created a blank elixir application and added enough code to cause the same behavior I'm seeing in my application. You can view it at

https://github.com/fastjames/hello_absinthe_client

Cloning the repo, then running mix deps.get && mix dialyzer should produce the dialyzer errors.

My hope is that I'm making a basic error in how I set up req and/or AbsintheClient.