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
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
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
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
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
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
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
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
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
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
(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
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex













Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
pierreabreup
I’m trying this Absinthe Root Query Pagination · GitHub but no success
benwilson512
You’re very close, you’re just making it harder than you need by employing
with. Thefrom_queryfunction already returns a tuple so the smallest change that would work is basically just:The
withis useless at this point though because it can’t fail, so we can simplify further do:One final question, how is the
source:going to bethread? This is a top level field, unless you’re setting the root value then the source is just an empty map.pierreabreup
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
withto make the code cleaner.About
:source, I don’t know the answer, but I’m doing some tests to understand how:sourceworks at this point.pierreabreup
Hi @benwilson512
Works like a charm!
I’ve used
Absinthe.Relay.Connection.from_listjust for tests propose. The correct solution is to usefrom_sliceIt is worth noting In this case,
source:is unuseful, as you had predict. Thesource:is used when you are listing associated object ( Absinthe.Relay.Connection — absinthe_relay v1.6.0 )