Fork me on GitHub

Is there a way to mutate the fulcro db continuously, like in a background loop, without making inspect turn blank? I think it does that if it's waiting on too many transactions


Looks like you should be able to remove-watch using the app uuid which is in your app state and then put the watch back after


hm, I wonder if I would break anything to have db-changed! ignore certain keys


After upgrading to Fulcro 3.6.0, I'm still getting the "Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17. Learn more:".


I see, I need to manually enable it.

👍 2

@holyjak here is something that confused me about your article You go into detail about "establishing edges in the client DB graph using initial-state". This is a fairly complicated thing, especially for a newbie (not that its bad design, like tony says, we are solving hard problems). Your explainer bubble is great on this topic (screenshot 1). However in example 7, you don't include the initial state piece required to make this work :root/accounts is never connected to anything (screenshot 2). If you copied and used this example, it would not work because its lacking the piece of data you described in screenshot 1. You don't need to include every detail in this small example, but this crucial detail is also not in one of your ;;LEFT OUT comments. Let me know if i'm misunderstanding something...

Jakub Holý (HolyJak)13:02:34

Thanks a lot for pointing out the problems, Tommy! I have now fixed it - see the site or

🙂 2