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 …

Nope, all you need is something like this: defmodule ParseBehavior do # Obviously replace any with your data types @callback parse(data :: any) :: any end defmodule CustomerA do @behaviour ParseBehavior end If you don’t implement the specified callbacks you will get a compilation warning. …

[image] CharlesO: response = apply(@some_module_from_config, :parse, [data]) No need to use apply as it’s much more useful if you have function name stored in variable. ` response = @some_module_from_config.parse(data)` [image] CharlesO: Is there a benefit for example to …

I also recommend watching the keynote from José https://www.youtube.com/watch?v=agkXUp0hCW8 He goes into the topic what to use when.

How does your code branch on input data and decides which module to use? I just recently had to do this and since I did not have a lot of modules and not too many input shapes I just made a router / dispatcher module that basically pattern-matches on the input and calls different module + function …

I’m trying to understand you point sir. Say I have more functions in handler module, and i want to ensure that every customer module implements all the functions correctly, then just like GenServer we coukd use @behavior correct?

In my case i have the same app deployed to different customers. Each customer has specific processing they need. I implement a module per customer, then in config, i have a customer_module_name setting. In this module, i do the customer specific processing. The main app, looks for module name, t…

Sounds like what I did but with multiple dispatchers (one per customer). Why are you not satisfied with that solution?

Behaviours are well documented, so it would be easiest to check it out. For example here is a quote I was referring to: If a module adopting a given behaviour doesn’t implement one of the callbacks required by that behaviour, a compile-time warning will be generated. Source: Behaviours | Typespec…

[image] CharlesO: Is there a benefit for example to have a @behaviour in Handler which defines :parse and other functions The major benefit is compile-time checking: if CustomerA says @behaviour Handler but doesn’t supply callbacks with the correct arities, the compiler will complain (somet…

Please can you point to a simple reference implementation? I’ve not written this type of behavior module before. I understand it requires macros, yes?

[image] 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 …

Elixir Programming Language Forum

A better Module interaction pattern?

Questions & Help Questions

CharlesO October 14, 2024, 1:31pm 12

Please do you know how to setup the behaviors code?