1stSolo

1stSolo

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.

Showing Posts 1 to 2

1stSolo

1stSolo OP

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…

1stSolo

1stSolo OP

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.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
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
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
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
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
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
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews