hawkyre

hawkyre

I want to create some kind of procedure to programmatically transform a changeset’s errors into my own error codes so that I can display them in the frontend.

I’ve come up with the following:

def create(%{} = course) do
  case Course.create(course) |> Repo.insert() do
    {:ok, course} ->
      {:ok, transform(course)}

    {:error, changeset} ->
      errors = parse_errors(changeset)
      {:error, errors}
  end
end

def parse_errors(changeset) do
  errors = changeset.errors
  parsed_errors = []

  parsed_errors = parse_single_error(errors[:tag], :unique, "COURSE_TAG_TAKEN", parsed_errors)

  parsed_errors
end

def parse_single_error(nil, _constraint, _error_msg, error_list) do
  error_list
end

def parse_single_error(error, constraint, error_text, error_list) do
  {_error_msg, constraints} = error

  if constraints[:constraint] == constraint do
    error_list ++ [error_text]
  else
    error_list
  end
end

I’m mostly looking for feedback on this since it’s the first time I’ve tried to parse errors like this and I have no idea whether there are better ways to achieve this or not.

Showing Posts 1 to 2

soup

soup

Without proofing the actual execution, it’s not unreasonable to do this.

You may also want to look at add_error as well as traverse_errors.

Most of my code has separate schemas for the data layer (business logic focused) and UI layer (user interface focused, may combine or obscure mulitiple data layer schemas - ex: data layer price is always cents but the ui layer changeset may accept dollars + cents), so with that in mind I would probably attach the error-code stuff to that as just another validation step. I may Enum.reduce(changeset.errors, changeset, ...) and just insert the error code into the existing errors.

I also would tend to return {:error, changeset} only because of convention, vs {:error, errors} but this is really code base specific – just be consistent.

hawkyre

hawkyre OP

I’m not using phoenix so I need to parse the errors anyway in the frontend. Some of the things you mention I assume are automatically handled by phoenix if you return a changeset with errors somehow to the frontend

— 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
water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
katta
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
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

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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews