pierreabreup

pierreabreup

This is my schema:

defmodule ContentProxyGraphql.Schema.ObjectTypes.Content do
  use Absinthe.Schema.Notation

  import_types Absinthe.Type.Custom
  import_types ContentProxyGraphql.Schema.ObjectTypes.{
    Person,
    Language,
    Publisher
  }

  alias ContentProxyGraphql.Resolvers

  object :content do
    field :type_of, non_null(:string)
    field :name, non_null(:string)
    field :date_created, non_null(:datetime)
    field :date_modified, non_null(:datetime)
    field :learning_resource_type, non_null(:string)
    field :description, :string
    field :thumbnail_url, :string
    field :license, :string
    field :educational_use, :string
    field :interactivity_type, :string
    field :url, :string
    field :author, list_of(:person)
    field :additional_property, list_of(:property_value)
    field :educational_alignment, list_of(:alignment_object)
    field :identifier, non_null(:property_value)
    field :publisher, :publisher
    field :in_language, :language
    field :audience, :education_audience
    field :is_part_of, :content_reference
  end

  object :property_value do
    field :type_of, non_null(:string)
    field :property_id,  non_null(:string)
    field :value, non_null(:string)
  end

  object :education_audience do
    field :type_of, non_null(:string)
    field :education_role, non_null(:string)
  end

  object :alignment_object do
    field :type_of, non_null(:string)
    field :alignment_type, non_null(:string)
    field :educational_framework, non_null(:string)
    field :target_name, non_null(:string)
    field :target_url, :string
  end

  object :content_reference do
    field :type_of, non_null(:string)
    field :identifier, :property_value
  end

  object :content_queries do
    field :contents, list_of(:content) do
      arg :type_of, :string
      resolve &Resolvers.Resources.Content.list/2
    end
  end


end

When I doing a query, I get this result:

I’m struggling to implement absinthe pagination on root object (in my case :content) because all of absinthe examples are about nested objects ( Absinthe.Relay.Connection — absinthe_relay v1.6.0 ). Is there a way to implement root object pagination?

To exemplify my problem, I want this exact pagination

Showing Posts 1 to 4

pierreabreup

pierreabreup OP

I’m trying this Absinthe Root Query Pagination · GitHub but no success

benwilson512

benwilson512

Author of Craft GraphQL APIs in Elixir with Absinthe

You’re very close, you’re just making it harder than you need by employing with. The from_query function already returns a tuple so the smallest change that would work is basically just:

thread_id = get_thread_id(thread)
with  thread <- Messages.find_all_threads_query(thread, user, uuid) do
  Absinthe.Relay.Connection.from_query(thread, &WkGraphql.Repo.all/1, p_args)
else
    {:error, error} -> {:error, error}
    _ -> {:error, "Error fetching Threads"}
end

The with is useless at this point though because it can’t fail, so we can simplify further do:

thread
|> Messages.find_all_theads_query(thread, user, uuid)
|> Absinthe.Relay.Connection.from_query(thread, &WkGraphql.Repo.all/1, p_args)

One final question, how is the source: going to be thread? This is a top level field, unless you’re setting the root value then the source is just an empty map.

pierreabreup

pierreabreup OP

Hi @benwilson512
first of all, thank you very much to read my message and answer this post.

I can’t use from_query because my data source is mongodb, I’m trying to use from_slice (Absinthe.Relay.Connection — absinthe_relay v1.6.0).

I will remove with to make the code cleaner.

About :source , I don’t know the answer, but I’m doing some tests to understand how :source works at this point.

pierreabreup

pierreabreup OP

Hi @benwilson512

Works like a charm!

connection field :contents, node_type: :content do
      resolve fn
        pagination_args, _ ->
          Resolvers.Resources.Content.list(pagination_args)
          |> Absinthe.Relay.Connection.from_list(pagination_args)
      end
    end

I’ve used Absinthe.Relay.Connection.from_list just for tests propose. The correct solution is to use from_slice

It is worth noting In this case, source: is unuseful, as you had predict. The source: is used when you are listing associated object ( Absinthe.Relay.Connection — absinthe_relay v1.6.0 )

object :person do
  field :first_name, :string
  connection field :pets, node_type: :pet do
    resolve fn
      pagination_args, %{source: person} ->
        Absinthe.Relay.Connection.from_list(
          Enum.map(person.pet_ids, &pet_from_id(&1)),
          pagination_args
        )
      end
    end
  end
end
— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
itzmidinesh
Hi all, I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
leoschweizer
Hi, we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
csmr
Hi all, I’m new here and would like to hear peoples views on my Elixir/Phoenix based game-engine! :smiley: Mutonex gamedesign was finish...
New
Stef-Verniers
Hello I’ve been coding in Elixir for almost two years now because of my current job where we implemented Elixir in our application. But ...
New

Other Trending Topics Top

dominicletz
Hey there, I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first. ...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
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
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
OndrejValenta
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly) AI dream has many faces, but general...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews