1stSolo

1stSolo

How to get Absinthe Resolution for Ecto struct?

I have a processing pipeline, and an ecto struct that gets passed around between stages. In each stage’s entry and exit, status field in the ecto struct gets updated and notification is sent to subscribers:

payload = my_ecto_struct
Absinthe.Subscription.publish(MyWeb.Endpoint, payload, status_changed: topic)

Herein lies a problem: publish/3 needs to take either absinthe resolution or list of fields: Absinthe.Subscription — absinthe v1.11.0

This is very different from queries and mutations where my Resolver could return {:ok, my_ecto_struct} and some magic happens behind the scene where fields are resolved from Ecto into Absinthe Schema’s object before it’s returned to GraphQL client in the form of Json.

So how do I get an absinthe resolution for my_ecto_struct so I can publish/3 it?

One of the reasons I need some translation from ecto to absinthe is because not all fields match between ecto schema and absinthe schema, for example, absinthe has user that is resolved via UserResolver using ecto schema’s user_id, and signature that is resolved from absinthe context and is not present in ecto struct.

First Post! Switch mode

1stSolo

1stSolo

I was thinking of a custom resolver for subscriptions:


  object :my_struct_subscriptions do
    @desc "Subscribes to status changes"
    field :my_struct_status_changed, non_null(:my_absinthe_object) do
      arg(:id, non_null(:id))
      config(&MyStructResolver.sub_config/2)

      trigger([:status_changed], topic: fn _ -> "status_changed" end)
      resolve(&MyStructResolver.resolve_status_change/3) # <-------
    end
  end

and then in the Resolver,

  def resolve_status_change(value, args, _absinthe_resolution) do
      value
      |> Map.from_struct()
      |> Map.delete(:__meta__)
      |> Map.put(:user, User.get(value.user_id))
      |> Map.put(:status, StatusResolver.get_status(value))
      |> Map.put(:signature, SignatureUtils.generate(value))
    else
      nil
    end
    {:ok, value}
  end

But seems like publish/3 is used mostly for notifying on a handful of fields and not a large object, and I would hate to have to change this bit of code every time schema changes and making sure that every field that requires special handling and can’t be passed in verbatim is resolved separately. I wish there was a utility/helper function to resolve ecto struct into Absinthe object just like the framework already does it for mutations and queries…

Last Post!

1stSolo

1stSolo

Seems like publish/3 was not meant for sending an entire object, but rather a few select fields. So I abandoned the idea of resolving an Ecto struct and just sending a few fields that change as the object passes through the processing pipeline - like status and a few datetime fields.

Where Next?

Trending in Questions Top

jonnycharles
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
spammy
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
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
saveman71
Hello ! We want new/edit form pages to POST/PUT to their own URL rather than the resources REST defaults (post /things, put /things/:id)...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
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
michallepicki
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 Top

JesseHerrick
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
ausimian
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
type1fool
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
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement