GenericJam

GenericJam

I’m trying to find a cleaner coding style for what I’ve got happening repeatedly in my code right now. This is looking very pyramid of doom-ish

# Variables in scope
%{ var1: var1, var2: var2, var3: var3}
case function1(var1) do
    # Success case one
    {:ok, %{pattern1: _}} ->
      case function2(var2) do
        {:ok, %{pattern2: _}} ->
          # Etc with the nesting as need be
          Logger.info()

        other ->
          Logger.error("Oops")
      end

    # Success case two
    {:ok, %{pattern3: _}} ->
      case function3(var2) do
        {:ok, %{pattern4: _}} ->
          # Etc with the nesting as need be
          Logger.info()

        other ->
          Logger.error("Oops")
      end

    # Failure case
    other ->
      Logger.error("He's dead, Jim. Cause of death: #{inspect(other)}")
  end

I know that as an alternative I could put the pattern matching/fail catching in a series of functions but this isn’t necessarily any more readable as the functions should be grouped by name not by logical association. Once the logic gets more complicated, it is actually worse imo for readability.

Is there some alternative I’m missing?

Showing Posts 1 to 5

preciz

preciz

LostKobrakai

LostKobrakai

You have a tree of cases here (not one happy path, different leaves between both first level successes), so unless you move stuff into functions (anonymous or named) you’d probably need to stick with what you have.

GenericJam

GenericJam OP

Yes. I didn’t actually realize until it was pointed out to me that with with you can pass the results from one call into the next one. The catch is that the errors become more grouped together which in some cases is beneficial. It seems like with is probably the happy medium here.

Thanks for the suggestion!

cnck1387

cnck1387

Just for future searches, would you mind including the with version so we have a before and after?

GenericJam

GenericJam OP

Here’s a rough translation although not direct as in the original I’ve got two success cases where only the first one will match whereas in the translation both with (potentially) match. This is the general idea though:

%{var1: var1, var2: var2, var3: var3}

    with {:ok, %{pattern1: _}} <- function1(var1),
          # Now you can use pattern1
         {:ok, %{pattern2: _}} <- function2(%{pattern1: pattern1, var2: var2}) do
      # Etc with the nesting as need be
      Logger.info()
    else
      # Failure case
      other ->
        Logger.error("He's dead, Jim. Cause of death: #{inspect(other)}")
    end

    with {:ok, %{pattern3: _}} <- function1(var1),
         {:ok, %{pattern4: _}} <- function3(var2) do
      # Etc with the nesting as need be
      Logger.info()
    else
      # Failure case
      other ->
        Logger.error("He's dead, Jim. Cause of death: #{inspect(other)}")
    end
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
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
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; 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

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews