wintermeyer
I have a social media setup where a User resource can like or block an other User resource. Here is the beginning of the resource:
defmodule Animina.Accounts.Reaction do
use Ash.Resource,
data_layer: AshPostgres.DataLayer
attributes do
uuid_primary_key :id
attribute :name, :atom do
constraints one_of: [:like, :block]
end
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
I want to like, unlike, block and unblock from within our own code and open an external JSON-API for 3rd party software to do the same.
Is it a good idea to create custom actions (like, unlike, block and unblock) for that? If yes, how? If no, why?
The documentation is too abstract for a mediocre programmer like me who works best with examples.
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
Yes, you should create “semantic actions”, i.e
like,unlike,block,unblockovercreate,update, anddestroy. When you connectAshJsonApi, you will tell it which actions to make available over the JSON:API.wintermeyer
Is it best/cleanest to do this with this resource (the resource which gets created) or would it be better to create those actions into the
Userresource since I want to block/like a user?zachdaniel
There will never be exactly one right answer for this question that applies in all cases, but in Ash(especially in 3.0 with code interfaces on the domain), you are free to define actions in the “most structurally convenient” way, and then expose consistent interfaces. In other words, callers don’t care where the action is defined. Since
likecreates aLike, it’s easiest to define it as a create action on that resource. Same for destroy.So, in short, best to define on the resource you’re manipulating directly, as opposed to defining it on a conceptually related thing. You’re are “liking a user”, but mechanically that is “creating a like”. If you end up wanting to make an action on user that delegates to this action, you’ll need this one anyway, so start there.