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
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Latest Phoenix Threads
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #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 )