I had a working app, using re-frame and re-com. I've tried to split it apart, putting reg-event-db, reg-sub, and rendering functions into their own namespaces and now it's stopped working. Inside this app, I have a re-com horizontal-tab component. When I get the on-change event from the horizontal-tab component, I post an event saying that the tab has changed, passing it the value of the new tab. I've confirmed that the function registered via reg-event-db for this event processes this event by updating the database value for it. However, the reg-sub function that this change should trigger doesn't seem to be getting called anymore. Is there some reason why putting the functions in different namespaces would impact things this way? Or do I just have a different bug in my code that I need to look for?

shooting from the hip, but you’re using events like ::thing and when you changed the namespace you’re using ::thing in two different namespaces but that now refers to two different keywords

Yeah, also check your browser's JS console for any warnings from re-frame.

I am using the single-colon form on the event/subscription keywords. I don't have any errors in the JS console.

I tried adding namespace prefixes to all out-of-namespace references, but that did start throwing errors in the JS console. I assumed that meant I was on the wrong track. I've looked at a few examples of real-world re-frame code and breaking things up like this should work fine. Maybe the reg-sub declarations aren't being processed because the compile/load process doesn't execute them? I've required all three new namespaces in my main file, but it's not clear to me whether this code is being compiled into the application. Right now, all I see in the compiled code is the code from my main function. I would assume that I would need to modify my shadow-cljs.edn file to compile/call all of these additional functions.