re-frame

rolt 2026-06-16T07:41:07.644779Z

https://github.com/day8/re-frame2/blob/main/docs/EP/EP-0004-subscription-inputs.md#no-app-db-dependent-topology I like having the views code as simple as possible, so we usually have some view specific subs, sometimes specific to the layout, and some reusable, more business oriented subs. I understand that the fixed dependency graph can be of great help for analysis and tooling, but do you think a custom version of re-frame2 could work while allowing dynamic inputs subs ?

2026-06-16T13:43:21.815449Z

@rolthiolliere are you saying you want to be able to do something like this:

(rf/reg-sub :current-page/view-model
    (fn [db _]
      (case (:route/name db)
        :article [[:article/page (:article/id db)]]
        :settings [[:settings/page]]
        :home [[:home/feed]]))
    (fn [[page-model] _]
      page-model))

rolt 2026-06-16T13:54:20.588789Z

no it's more something like this:

(reg-sub :current-page/view-model
  (fn [_]
    [[:article/by-id @(subscribe [:current-page/article-id])]
     [:user/by-id @(subscribe [:current-page/user-id])]
     [:subject/by-id @(subscribe [:current-page/subject-id])]])
  (fn [...]))
and avoid having to call [:current-page/article-id] etc in the view to pass the value to view-model

Aleed 2026-06-16T14:17:47.322289Z

Do you ever feel trapped into coding with AI? Or alternatively, do you see a reason for going back to regular coding?