Hello everyone, I read some Elixir books and I did some small toy projects with Elixir. My mind is still too object oriented programming but I want to start creating “real code”, specifically, I’d like to create shrinerb in Elixir. It is an awesome library that I use in Ruby and I think it could be…

If I am understanding your query correct, I think what you want to look into are Behaviours: [image] Writing extensible Elixir with Behaviours Learn how to write extensible Elixir with Behaviours: when they should be used and why you'd want to use them. htt…

Hello @aseigo , thank you for your response, I wanted something a little bit more complex, I need more composition. This small example in Ruby maybe helps: class UploaderBase def upload(io, options) store.upload(io, options) end def delete(name) store.delete(name) end end class Pl…

So, there is the super function that does what you want with behaviours: Kernel.SpecialForms — Elixir v1.20.2 You can also use the using and import directives to extend modules in nicely generic ways: Home Personal blog of Yos Riady. Yos is a Sof…

Interesting. I felt the use of super/defoverridable not very idiomatic and you feel the same. That was a doubt I had. The key point is the user of the library. He can create the uploader he wants only adding small pieces of code packaged in plugins. Currently shrine has 43 plugins! The user can as …

[image] alexcastano: I felt the use of super/defoverridable not very idiomatic and you feel the same. defoverridable is quite idiomatic and used quite a bit. It is the use of super that is less so. Rather than going to the implementation of the function in the re-implementation, it usually ex…

I don’t think this is what you’re after - but just in case - eplugin has a totally different approach to plugins. There is a dedicated gen_server process that is responsible compiling the plugins and managing their particulars in ETS tables.

I just do plugins via gen_event, isn’t that the easiest and most built-in way? Literally I just send an event at whatever hook points I want and let whatever is listening to them do whatever they want at that point. gen_event has it’s share of problems that I fixed in an erlang replacement library…

[image] OvermindDL1: Does Elixir have a GenEvent that uses monitors? GenEvent is in the process of being deprecated Plataformatec: Replacing GenEvent by a Supervisor + GenServer

[image] peerreynders: GenEvent is in the process of being deprecated Oh thank goodness! It is about time! [image] peerreynders: Plataformatec: Replacing GenEvent by a Supervisor + GenServer >.> Uh, so basically what mine already is… I wonder if I should just rewrite it in Elixir an…

[image] aseigo: The exact same thing can be achieved by providing properly named functions that get called. In the example of an overridable upload function, plugins that wish the default behavior can just call Base.upload directly, with an alias Uploader.Base in the Uploader.base’s using macro …