Yes, I pulled recent :local/root for fulcro, so beta 3. I'll see if I can make a repro case, but note that I'm using two :target, one for where I want to merge the data, one for the target-ready.

I have some data coming from an API that is deeply nested and I want to use it as a form. Ideally I’d like to pass the data back as it came when the form update is complete, so I don’t want to modify it on my backend before passing to my front end form. How would one recommend implementing deeply nested form fields? For example I could see something like {:foo {:bar {:baz "quux"}}, where I want to update baz’s value and maintain the shape of my data. One thought I had was to not use the m/set-string! style helpers and just write the mutations myself w/ update-in/assoc-in, etc..

componentWillReceiveProps is deprecated https://github.com/fulcrologic/fulcro/blob/develop/src/main/com/fulcrologic/fulcro/dom.cljs#L140 https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html

@souenzzo has been for some time…like over a year I think

Hey, I've just created an issue for recursive queries not working together with dynamic router: https://github.com/fulcrologic/fulcro/issues/320 Just letting you know here on slack. I'm not sure if you prefer slack or gh for bug reports but it was more convenient for me to make it there.