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
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 2 of 2 Posts
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