CharlesO
I’m looking to improve this pattern.
It is a pattern I use in a lot of my projects.
defmodule Handler do
def handle_request(data) do
response = apply(@some_module_from_config, :parse, [data])
# do_something_with_response(response)
...
end
end
I then have customer specific implementations of :parse in separate modules, for example
defmodule CustomerA do
def parse(data) do
# specific parsing of this data for Customer-A
end
end
defmodule CustomerB do
def parse(data) do
# specific parsing of this data for Customer-B
end
end
This works, but can it be improved?
Is there a benefit for example to have a @behaviour in Handler which defines :parse and other functions
Then each Customer module no implements use Handler
Please are their better patterns for doing this?
Thanks.
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
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
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
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
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
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
- #hex
- #security
- #metaprogramming










Marked As Solved- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
D4no0
Nope, all you need is something like this:
If you don’t implement the specified callbacks you will get a compilation warning.
You can also have the variant with the default implementation:
I wouldn’t recommend using the variant with default implementation unless that is strictly required, as it makes the code harder to read.
Also Liked
al2o3cr
The major benefit is compile-time checking:
CustomerAsays@behaviour Handlerbut doesn’t supply callbacks with the correct arities, the compiler will complainAs a side bonus, libraries like
moxcan use that same behaviour for their definitions.Eiji
No need to use
applyas it’s much more useful if you have function name stored in variable.Not only it would not give you any benefit, but it would also be wrongly used.
In
Handlermodule you have to define callbacks and / or macrocallbacks. You use@behaviourattribute inCustomerAandCustomerBmodules. In this tiny example it’s not important at all, but in general you use this to make sure that all callbacks are implemented asElixirgives compilation warning otherwise.egze
I also recommend watching the keynote from José https://www.youtube.com/watch?v=agkXUp0hCW8
He goes into the topic what to use when.
Last Post!
D4no0
You can’t, the module that defines behavior whole point is to make sure that you are implementing the required functions, it’s up to you how you call them afterwards.
You can either use the pattern you are already using with
apply/3or you can call directly the function, as module names are just plain atoms:You could add some compile-time checks to ensure that the module you are calling has the behavior declared, but I don’t see a lot of value from that.