oliveiragahenrique
I’m designing a pure functional data structure to manage banking accounts, a simplified version of it would be:
defmodule Account do
defstruct balance: 0, limit: -500
def new() do
%Account{}
end
def deposit(%Account{} = account, amount) do
new_account =
%Account{account | balance: account.balance + amount}
{:ok, new_account}
end
def withdraw(%Account{} = account, amount) do
new_balance = account.balance - amount
if new_balance >= account.limit do
new_account =
%Account{account | balance: new_balance}
{:ok, new_account}
else
{:denied, "No funds", account}
end
end
end
My question is about when should I use the response pattern of {:ok, data} for sucess and {:error, reason, unchanged_data} for failures.
This sounds like the way to go here on this problem, but if I go with this pattern I lose the feature of do something like this:
account =
Account.new()
|> Account.deposit(%{amount: 5000})
|> Account.deposit(%{amount: 3000})
|> Account.withdraw(%{amount: 1000})
I really like to design modules that could use the pipe operator like this, but how to do this when the module functions can fail?
If I just remove the :ok from the sucess response would solve the problem, but is this a good pattern?
What you guys think? How can I keep the pipe feature together with a good response check validation?
Trending in Questions
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
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
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
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
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
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
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
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
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kokolegorille
If the pipeline can break, I would use with…
bottlenecked
@rrrene has written a series of articles on data flow patterns that perhaps could help. You may want to read up on the Token-based approach for your specific use case.
oliveiragahenrique
Great tip! Gonna check it out later for sure!