Conversation
|
If I remember correctly, I had the same issue with child components when I tried to update to the latest version of jsoo-react a few months ago. I think #8 should be fine for now. jsoo-react isn't stable yet anyway, so this probably won't be the last breaking change they make. |
|
By the way, the also mentioned that there might be a compatibility library for this big breaking change at some point: ml-in-barcelona/jsoo-react#162 (comment). |
2160af7 to
cdd38f5
Compare
cdd38f5 to
95a22ef
Compare
|
I rebased Simmo's work on a more recent version of the master branch, removed the opam pin such that we should now be using the opam release of jsoo-react directly, fixed the above mentioned compilation error with the |
If you use the |
95a22ef to
7f576f8
Compare
|
@sim642 Since you worked on this initially, it might make sense if you review it. (I cannot request you as you are the one who started the PR.) |
|
This seems to work fine with the Or maybe this profile issue exists already before this PR? |
|
I discovered this warning before but was not able reconstruct it. If I remember correctly, it was due to |
|
I checked that for me it also happens on |
|
Nevermind, I somehow had pinned jsoo-react to the old one again I guess. Somehow I'm now getting this error when building GobView: So I guess there's some excessive |
This is the original version of #8.
Unfortunately jsoo-react has lots of breaking changes in the meanwhile. I think I managed to fix most of the compilation error, but there's one left which I don't really understand. There seems to be some change to the children representation, which requires weird
...unpacking on all out custom components.TODO
ErrorBoundaryusage compilation.