kylevsteger
Hey all! I’m having trouble with Absinthe and Dataloader when trying to resolve friends of a user.
I was able to load the friends without much issue, but now I’m trying to add a status to the response, which lives on the join table.
The last chunk in the code below is where I’m struggling. Any insight is much appreciated! Thanks!
# User Ecto Schema
@primary_key {:id, :binary_id, autogenerate: true}
schema "users" do
...
has_many :friends_assoc, Friend, foreign_key: :user_id
has_many :reverse_friends_assoc, Friend, foreign_key: :friend_id
has_many :friends, through: [:friends_assoc, :friend]
has_many :reverse_friends, through: [:reverse_friends_assoc, :user]
end
# Friend Ecto Schema
@primary_key {:id, :binary_id, autogenerate: true}
schema "friends" do
field :status, FriendStatus
belongs_to :user, User, type: :binary_id
belongs_to :friend, User, type: :binary_id
end
# User Absinthe Schema
object :user do
field :id, non_null(:string)
...
field :friends, list_of(:friend) do
arg :status, :friend_status
# This ultimately points to: `Dataloader.Ecto.new(Repo, query: fn _, args -> generate_query(args) end)`
resolve dataloader(User)
end
end
# Friend Absinthe Schema
object :friend do
field :id, :string
field :first_name, :string
field :last_name, :string
# This comes back as `null` on the GraphQL response
# because it's not on the Ecto User schema
# but I'm not sure how to remedy the situation
field :status, :friend_status
end
UPDATE
I wound up going with a custom Dataloader.KV that points to this function
@doc """
Queries the database for Users and loads their friends.
"""
@spec get_friends_with_status([Ecto.UUID.t()], map()) :: map()
def get_friends_with_status(ids, %{status: status} = _args) do
query = from u in User,
left_join: fa in assoc(u, :friends_assoc),
left_join: fr in assoc(fa, :friend),
where: u.id in ^ids,
where: fa.status == ^status,
select: %{
user_id: u.id,
friend: %{
first_name: fr.first_name,
last_name: fr.last_name,
email: fr.email,
id: fr.id,
status: fa.status
}
}
id_map = Map.new(ids, & {&1, []})
query
|> Repo.all()
|> Enum.reduce(id_map, fn %{user_id: user_id, friend: friend}, acc ->
Map.update(acc, user_id, [friend], fn
friends -> [friend | friends]
end)
end)
end
Trending in Questions
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
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
When I use Mix.install with a git dependency, using git@github.com:... how do I change the SSH identity used?
I’ve got two Github accoun...
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
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
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
(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
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #elixirconf-us
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
fuelen
Hello!
Personally I would go with another graphql schema.
:friendobject is context-specific. It has anidof the user, but differentstatusdepending on parent record. This is error-prone, because GraphQL client on frontend side MAY use simple caching byidfield only, so other users may borrow friends.To avoid this you have to use an
idfrom thefriendstable. But it would be simpler to expose:userassociation:kylevsteger
Thanks for the suggestion! I would up going with this implementation