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
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
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
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
Other Trending Topics
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
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
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
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










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!