pwightman

pwightman

I’ve recreated a minimal example of the problem I’m experiencing, where cast_embed on a embeds_many is trying to protect me from accidentally overwriting my embeds when I don’t want it to. Given the following code:

defmodule TaskList do
  primary_key false
  embedded_schema do
    embeds_many :tasks, Task
  end

  def changeset(data, params \\ %{}) do
    data
    |> cast(params, [])
    |> cast_embed(:tasks)
  end
end

defmodule Task do
  @primary_key false
  embedded_schema do
    field: title
  end

  def changeset(data, params \\ %{}) do
    data
    |> cast(params, [:title])
    |> validate_required(:title)
  end
end

# Below called when LiveView form submitted

def handle_event("submit", params, socket) do
  # task_list already has 3 Task structs assigned to `tasks`, when loaded from DB
  task_list = socket.assigns.task_list

  result =
    task_list
    |> TaskList.changeset(params["data"])
    |> Repo.update()

  case result do
    {:ok, task_list} ->
      # redirect, etc
    {:error, changeset} ->
      # handle error
  end
end

TaskList.changeset/2 will raise an exception because I’m trying to replace the existing 3 Task embeds with new ones, and on_replace defaults to :raise.

Elsewhere in my app, I’m using embeds_one :foo, Foo, on_replace: :update , which has exactly the semantics I want, however embeds_many does not support this option, and none of the available options (:raise, mark_as_invalid, :delete) has the correct semantics. I would just like any cast_embed(:tasks) to “update/replace” what is there.

Right now I’m doing a dance where I replace the existing list with an empty list if I will be calling cast_embed, but it feels like a hack, and I’m replicating this hack in multiple places, and it makes the code quite messy and hard to reason about (esp when there’s other logic that conditionally calls cast_embed).

Any ideas how to do this simply?

First 3 of 3 Posts Switch mode

al2o3cr

al2o3cr

This sounds like the embedded-schema version of the difference between cast_assoc and put_assoc; I’ve never used it, but would put_embed solve this?

LostKobrakai

LostKobrakai

If you don’t use primary keys what would be the difference between on_replace: :delete and on_replace: :update in the first place? This is besides the fact that for embeds_many you cannot use :update for replaced items, because there’s no way to know which old item shall be updated with which set of new data. Even less given you don’t have primary keys on your embeds.

pwightman

pwightman OP

You are correct, :delete has the semantics I was looking for, but something else in my code led me to believe it was “deleting” them in a way I wasn’t expecting. It wasn’t. Thanks for the push to look back at that approach!

— All posts loaded —

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
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
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
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
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
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
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
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

We're in Beta

About us Mission Statement