fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
nivekuil 2021-06-19T20:25:48.212200Z

3.5 seems to have changed something with the ordering of renders/transactions, not sure if it's intended. the effect I'm seeing is clerk is not restoring to the same scroll position as before under some circumstances (it needs the transaction containing clerk/after-render! to run after all renders). pretty subtle to try to repro unfortunately but I'll take a deeper look if it's a bug

tony.kay 2021-06-20T16:59:53.216100Z

I do not see any reason why that would have changed.

nivekuil 2021-06-29T05:07:17.309400Z

I think this was a caching issue. I can repro it if I pull my local fulcro repo from 3.4->3.5 and let shadow recompile but not with a clean build

tony.kay 2021-06-19T20:32:51.212900Z

See note on release: after-render was moved. I left a deprecated var in the old place, but it isn't used.

tony.kay 2021-06-19T20:33:09.213300Z

I should have probably just deleted it

tony.kay 2021-06-19T20:33:31.213500Z

and I have no idea what "clerk" is

nivekuil 2021-06-19T20:40:08.213700Z

clerk is https://github.com/PEZ/clerk. I'm not using the after-render dyn var, just the :after-render? key in the mutation opts, was that also affected?