It's a matter of support, mostly
Better REPL in what sense?
I’d like to be able to get the live state of a rendered component in my REPL, change it and trigger a re-render
evaluate an element in my REPL and see it rendered in a popup
or maybe many other things! I dont know 😛 I just want to be able to do more things with my editor + repl rather than have to live in editor + repl + app + chrome devtools
I have an experiment I did that got the currently rendered tree of some React root on the page, and turned it into a seq using tree-seq
then I could filter/map/etc. on it. with a bit of elbow grease I was able to get the currently rendered state of a specific element on the page and change it
it seems like a good opportunity for a library to fill in the gaps
it relies on a lot of internals of whatever version of React you’re using so I don’t think I would include it in helix, and I haven’t had time to really think about any use cases beyond the two I talked about
but I bet there’s a lot more
sounds like something that needs a custom rendedrer
like enzyme or other test renderers?
the two things I've written above shouldn't need a custom renderer at all. just needs to hook into the right things in React internally
I believe you ; )
https://github.com/pubkey/rxdb when rxjs is not enough ...