Thanks for the update, the explanation makes sense. I am no Drab expert let alone the creator so the following input is just to provide feedback from a user.
I read in the Drab.exec_elixir() documentation it requires the elixir function named in the first argument to be
- in the commander,
- to be a handler.
This lead me to expect it to act like the other handlers and have the default payload passed in and not behave differently based on the handler’s caller being drab-click() vs exec_elixir().
Leaving Drab.exec_elixir() unchanged and adding Drab.exec_handler() may continue the issue where a handler will act differently depending on how it is called, even though all three methods are designed to call handlers.
I am not sure whether changing Drab.exec_handler() might break someone’s code so can’t speak to the risk/value of changing it. I like that exec_handler is named more explicitly in that the called function is required to be a handler. So I guess I lean toward option 2, and maybe decide to keep unchanged and possibly deprecate exec_elixir() at some point unless it has some other purpose than calling handlers.
My 2c.
Thanks again for the great package, really enjoying it.
