x4K3PqNH

x4K3PqNH

Hi guys,

I have a GraphQL API via Absinthe where the relay/pagination part was implemented manually. Want to switch now to Absinthe.Relay and can’t figure out how to reuse a connection.

In a direct approach I define a connection into a file, the file is imported in the schema via import_types/1. Further I import the connection into every object it’s needed via import_fields/1 and everything works fine. If I switch to Absinthe.Relay and use the same steps, the connection is not available under the field, but I don’t get any compile warnings/errors.
I did put the connection inside an object so I have a name to import in import_fields/1, but without the object what name/atom should I use in the import_fields/1 to import the connection directly, if that’s even possible ?

Here’s what I think are the relevant parts in the current implementation (stripped to the bare minimum):

defmodule Api.Users.Types do
  use Absinthe.Schema.Notation

  object :group do
    interface(:node)
    ...
  end


  object :user_edge do
    interface(:edge)

    field(:cursor, non_null(:string))
    field(:node, :user)
  end


  object :user_connection do
    interface(:connection)

    field(:edges, list_of(:user_edge))
    field(:nodes, list_of(:user))

  end


  object :user_edge_connection do
    field(:users, non_null(:user_connection)) do

      ... arg(...) & resolve(...)

    end
  end
end



defmodule Api.Schema do
  use Absinthe.Schema
  
  import_types(Api.Users.Types)
  import_types(Api.Groups.Types)
  import_types(Api.Organization.Types)
  
  query(...)
end



defmodule Api.Groups.Types do
  use Absinthe.Schema.Notation

  object :group do
    ...
    import_fields(:user_edge_connection)
  end
end


defmodule Api.Organization.Types do
  use Absinthe.Schema.Notation

  object :organization do
    ...
    import_fields(:user_edge_connection)
  end
end

And here is the Absinthe.Relay way:

defmodule Api.Users.Types do
    use Absinthe.Schema.Notation                                                                                                                      
    use Absinthe.Relay.Schema.Notation, :modern 
    
    node object :group do 
      ...
    end
    
    
    connection node_type: :group
   
    object :user_edge_connection do
      connection field :user_connection, node_type: :user do     
        ... arg(...) & resolve(...)
      end
    end
end


defmodule Api.Schema do
  use Absinthe.Schema
  
  import_types(Api.Users.Types)
  import_types(Api.Groups.Types)
  import_types(Api.Organization.Types)
  
  query(...)
end


defmodule Api.Groups.Types do
  use Absinthe.Schema.Notation

  object :group do
    ...
    import_fields(:user_edge_connection)
  end
end


defmodule Api.Organization.Types do
  use Absinthe.Schema.Notation

  object :organization do
    ...
    import_fields(:user_edge_connection)
  end
end

  

We have connections that are reused in many parts, and if we need to define the connection and it’s arguments over and over again, in the long run it’s a high change they will be inconsistent.

Unfortunately did not found anything in the docs or any other resources online pointing me in the right direction here.

Thanks

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews