We ended up mostly breaking our event.cljs up into files under
events that matched our
views using namespaced keywords for the events. We kept the subs in a global subs file at least for now.
Whoa! What a super, super idea!!! Thank you!!!
Thanks so much for the suggestion, @rberger.
PS: as I’ve been studying what has been tripping me up in the events, one of them is the lack of “information hiding.”
In the global db, I have the raw list of Trello cards, and a “materialized view”, where filters are applied and other things I don’t remember. I had some events inappropriately accessing the raw list, instead of the materialized list…
I’m now pondering how to keep certain parts of code from seeing the raw card list, lest I make the same mistake again…
(Maybe I nest certain elements in the global db into an area called,
:private-do-not-look-or-touch` — as they are the “model,” not for the view?)
@devn Just posted the program I wrote to generate the “event dispatch graph” above — it has lots of obvious flaws, but I hope might be useful to someone! It definitely helped me! https://github.com/realgenekim/re-frame-event-graph3❤️