wintermeyer

wintermeyer

I have a Reaction resource which is used to store likes and blocks in a social media context (a user can like an other user). I want to create a like action but get the following error. How can I fix this?

iex(12)> like = Animina.Accounts.Reaction 
|> Ash.Changeset.for_create(:like, %{sender_id: user2.id, receiver_id: stefan.id}) 
|> Animina.Accounts.Reaction.create!()
** (Protocol.UndefinedError) protocol Enumerable not implemented for #Ash.Changeset<action_type: :create, action: :like, attributes: %{sender_id: "207a829e-2464-42f7-8257-f4fa482fc7c2", receiver_id: "096da9ff-bcf7-49a1-8cba-f98413f37cab"}, relationships: %{},

The resource:

defmodule Animina.Accounts.Reaction do
  @moduledoc """
  This is the Reaction module which we use to manage likes, block, etc.
  """

  use Ash.Resource,
    data_layer: AshPostgres.DataLayer

  attributes do
    uuid_primary_key :id

    attribute :name, :atom do
      constraints one_of: [:like, :block]
      allow_nil? false
    end

    create_timestamp :created_at
  end

  relationships do
    belongs_to :sender, Animina.Accounts.User do
      allow_nil? false
      attribute_writable? true
    end

    belongs_to :receiver, Animina.Accounts.User do
      allow_nil? false
      attribute_writable? true
    end
  end

  actions do
    defaults [:create, :read, :destroy]

    create :like do
      accept [:sender_id, :receiver_id]
      change set_attribute(:name, :like)
    end
  end

  code_interface do
    define_for Animina.Accounts
    define :read
    define :create
    define :destroy
    define :by_id, get_by: [:id], action: :read
    define :by_sender_id, get_by: [:sender_id], action: :read
    define :by_receiver_id, get_by: [:receiver_id], action: :read
  end

  identities do
    identity :unique_reaction, [:sender_id, :receiver_id, :name]
  end

  postgres do
    table "reactions"
    repo Animina.Repo

    references do
      reference :sender, on_delete: :delete
      reference :receiver, on_delete: :delete
    end
  end
end

Showing Posts 1 to 10

benswift

benswift

Looks like you are mixing up the changeset-based resource creation flow and the code interface one. Once you have a changeset, you just pipe it into ‘Ash.create!’.

Sorry about the terse reply, typing on my phone right now :slight_smile:

wintermeyer

wintermeyer OP

That doesn’t work either:

iex(3)> Animina.Accounts.Reaction 
|> Ash.Changeset.for_create(:like, %{sender_id: stefan.id, receiver_id: stefan.id}) 
|> Ash.create!

** (ArgumentError) No api configured for resource Animina.Accounts.Reaction.

Here just the changeset:

iex(3)> Animina.Accounts.Reaction 
|> Ash.Changeset.for_create(:like, %{sender_id: stefan.id, receiver_id: stefan.id}) 
#Ash.Changeset<
  action_type: :create,
  action: :like,
  attributes: %{
    name: :like,
    receiver_id: "16d7d94b-3975-4220-afc6-83d0ad009c9e",
    sender_id: "16d7d94b-3975-4220-afc6-83d0ad009c9e"
  },
  relationships: %{},
  errors: [],
  data: #Animina.Accounts.Reaction<
    receiver: #Ash.NotLoaded<:relationship>,
    sender: #Ash.NotLoaded<:relationship>,
    __meta__: #Ecto.Schema.Metadata<:built, "reactions">,
    id: nil,
    name: nil,
    created_at: nil,
    sender_id: nil,
    receiver_id: nil,
    aggregates: %{},
    calculations: %{},
    ...
  >,
  context: %{actor: nil, authorize?: false},
  valid?: true
>

Sorry about the terse reply, typing on my phone right now :slight_smile:

No worries. I am more than grateful that you type it on your phone. I know what a PITA that is.

frankdugan3

frankdugan3

Looks like you’re missing something like api: Animina.Accounts from your for_create.

zachdaniel

zachdaniel

Creator of Ash

This is advice for 3.0, as most 2.0 users will not have configured the api: Api option.

For Animina.Accounts.Reaction.create!(), that function is a code interface function which does not take a changeset. It takes the input directly

Animina.Accounts.Reaction.create!(%{sender_id: user2.id, receiver_id: Stefan.id})
wintermeyer

wintermeyer OP

I want to call the :like action which I defined here:

  actions do
    defaults [:create, :read, :destroy]

    create :like do
      accept [:sender_id, :receiver_id]
      change set_attribute(:name, :like)
    end
  end

If I just call Animina.Accounts.Reaction.create!/1 I get this error because the name attribute is required.

iex(5)> Animina.Accounts.Reaction.create!(%{sender_id: stefan.id, receiver_id: stefan.id})
** (Ash.Error.Invalid) Input Invalid

* attribute name is required
    (ash 2.18.2) lib/ash/api/api.ex:2711: Ash.Api.unwrap_or_raise!/3

How can I call the like action? I tried this but that didn’t work:

iex(5)> Animina.Accounts.Reaction.create!(:like, %{sender_id: stefan.id, receiver_id: stefan.id})
** (FunctionClauseError) no function clause matching in Keyword.split/2    
    
    The following arguments were given to Keyword.split/2:
    
        # 1
        %{
          receiver_id: "16d7d94b-3975-4220-afc6-83d0ad009c9e",
          sender_id: "16d7d94b-3975-4220-afc6-83d0ad009c9e"
        }
    
        # 2
        [:changeset, :actor, :tenant, :authorize?, :tracer]
    
    Attempted function clauses (showing 1 out of 1):
    
        def split(keywords, keys) when is_list(keywords) and is_list(keys)
    
    (elixir 1.16.0) lib/keyword.ex:1179: Keyword.split/2
    (animina 0.1.0) deps/ash/lib/ash/code_interface.ex:536: Animina.Accounts.Reaction.create!/2
zachdaniel

zachdaniel

Creator of Ash

Ah, right, you don’t want to use the code interface function that you added for :create, I see now.

like = Animina.Accounts.Reaction 
|> Ash.Changeset.for_create(:like, %{sender_id: user2.id, receiver_id: stefan.id}) 
|> Animina.Accounts.create!()

I believe that you mean to be calling the function on the api, not the resource. The create function on the resource is defined by your define :create in the code interface, and its meant to cal specifically the create action.

wintermeyer

wintermeyer OP

Now I am totally lost. What is the cleanest solution for the given problem? I want for the future external JSON-API a way to create a like the most secure way. What is the best way to do so?

wintermeyer

wintermeyer OP

I opened a new question for this.

joelpaulkoch

joelpaulkoch

Did you try to make the like action part of the code interface?

Something like:

code_interface do
...
define :create_like, action: :like
end

And then call Animina.Accounts.Reaction.create_like or maybe it’s Animina.Accounts.create_like. This way you don’t need the name argument

zachdaniel

zachdaniel

Creator of Ash

You have a :like action, and so how you call it in code can’t and won’t affect how the JSON:API behaves (which is why Ash is the way that it is).

There are three ways to call this like action in code, one of which is no longer available in 3.0. AshJsonApi will be unaffected by your choice here. You should choose #1, but I’m including 2 & 3 informationally.

  1. You can define a code interface function as @joelpaulkoch says. This is the recommended approach. For this, you’d define something like this:
define :like, args: [:sender_id, :receiver_id]

and call it like YourResource.like(sender_id, receiver_id).

NOTE: In 3.0 this can be done in one additional way, where you define the code interface on the domain. It’s not relevant here, see the upgrade guide for more.

  1. You can build a changeset and then call YourApi.create not YourApi.Resource.create. This is deprecated in 3.0

  2. You can build a changeset and then call Ash.create. However, this only works if you have configured an api when using the resource, i.e use Ash.Resource, api: Api. (because we have to know the api). This is essentially a compatibility feature to make upgrading to 3.0. Don’t bother with it right now. When you are interested in upgrading to 3.0, the upgrade guide will explain how to make this change.

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
bradley
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
unaware8150
Hello folks! So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
Alvinkariuki
How Can I Optimise Compile Time Dependencies I have been building an elixir application for about 2 years now. Many modules and files ha...
New
leoschweizer
Hi, we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New

Other Trending Topics Top

mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
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
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New
budgie
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with. But I don’t use it anymore. Serverless was the promis...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews