Absinthe.Subscription.unsubscribe doesn't work about absinthe HOT 4 CLOSED

@michaelcaterisano Depending on what you are doing with those channel pids you could send them a message and then do it in a handle_info. Otherwise the solution you have seems fine to me.

from absinthe.

I ended up getting this to work by adding a handle_out function to absinthe_phoenix and sending an unsubscribe message directly to the channel. Is there a better way to handle this?

  def handle_out("unsubscribe", %{"subscriptionId" => doc_id}, socket) do
    pubsub =
      socket.assigns
      |> Map.get(:absinthe, %{})
      |> Map.get(:opts, [])
      |> Keyword.get(:context, %{})
      |> Map.get(:pubsub, socket.endpoint)

    Phoenix.PubSub.unsubscribe(socket.pubsub_server, doc_id)
    Absinthe.Subscription.unsubscribe(pubsub, doc_id)
    {:noreply, socket}
  end

sub_id = "some-sub-id-i-grabbed" 

broadcast = %Phoenix.Socket.Broadcast{
      topic: "__absinthe__:control",
      event: "unsubscribe",
      payload: %{"subscriptionId" => sub_id}
    }

Phoenix.PubSub.broadcast!(My.PubSub, "__absinthe__:control", broadcast)

from absinthe.

Hey @michaelcaterisano which process is calling unsubscribe? The caller of unsuscribe needs to be the process that also called subscribe, it can't be done from a different process.

from absinthe.

@benwilson512 I figured that was the case. I was definitely trying to call unsubscribe from a different process than subscribe. Do you have thoughts about the workaround above? Is there a better way to unsubscribe individual subscriptionIds?

from absinthe.