events & subs as defn

[niquola]

Hello, we are happy re-frame users for many years.

We are running tests on event handlers, subs, and pure components in jvm.
This is some reflection - you may throw away if not relevant.
Recently we started using macros on top of rf/reg-sub rf/reg-event-fx to define subs and event handlers as vars
to track deps explicitly and write a little bit less code.

(defs some-subs [db params]
    (get-in db ....))

(defx some-event [{db :db} params]
     {:fx ..., :db: ...})

(defview myview [some-sub]
    [:div {:on-click #(rf/dispatch [some-ev {..}])
         (pr-str some-sub)])

Here is an idea. Because event-handlers and subscriptions are pure cljc functions
why not define and dispatch them as functions (or vars with meta) in re-frame.
Without any special registry.

(defn some-event {:cofx {:some-key [:some-fx params}, :rf/path [:path :in :db]}
    [{sk :some-key db :db} params]
    {:fx ..., :db....})

(defn some-subs [db params] ....)

(defn some-comp []
  [:div {:on-click (rf/dispatch #'some-ev params)}
      @(rf/subscribe #'some-subs params)])

73's niquola

[mike-thompson-day8]

@niquola
I take your point that this approach is certainly possible. But I'm very comfortable using keywords for identities. After all, that's the reason they are in the language.

[niquola]

Thx @mike-thompson-day8
Just to argue: you do not use multi-methods everywhere in clojure code - you are using namespaces and functions :)

[mike-thompson-day8]

Yeah, I do understand what you are saying, but when it comes to these kinds of decisions, the boat has sailed years ago. A disruptive change would have to bring a massive upside.