munksgaard

munksgaard

`form_to` with multiple reference IDs: More "type" safety?

I’m working my way through the Ash book and got the chapter on creating an “album” that is associated with an artist. The book suggests that the way to handle passing in the associated artist when creating a new album involves the forms DSL from AshPhoenix. Here’s the specific snippet:

forms do
  form :create_album, args: [:artist_id]
end

This results in the creation of a form_to_create_album/2 function that takes an artist_id as the first argument. This of course works fine, but it worries me a bit that it takes a raw ID as the first argument (typically an integer or UUID). If there was more than one reference that needed to be added, there’s a non-zero chance that I’ll accidentally pass in the arguments in the wrong order without knowing about it.

In non-Ash projects in the past, I’ve taken to enforcing some additional safety in cases like this by having a function like form_to_create_album/2 take a %Artist{} as the first argument and pattern match on it to ensure that it’s correct. So, my question is, is that something that’s easy to do with Ash/AshPhoenix, or would it require custom actions or something? Or is this pattern simply not used in Ash?

I’m still very new to Ash, so please forgive my ignorance if this was a bad question.

First 2 of 2 Posts! Switch mode

zachdaniel

zachdaniel

Creator of Ash

I believe that if you keep reading you will see a mechanism to have special argument types for your code interfaces. That example could be adjusted to taking a struct at the interface level and an id at the action level :slight_smile:

munksgaard

munksgaard

I guess that’s what I get for my impatience. Thanks for your response!

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 & 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