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
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
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
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
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
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
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex










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