Just released Fulcro 2.6.0-RC1 to clojars.

Nearly full support for all new React 16.4 features. Only one missing: The new static lifecycle method getDerivedStateFromProps…that one is going to take some tinkering to get it to pass through the macros ok.

Book updated

@tony.kay nice! hey, I think we should also add fragments to this version before release

oh yeah…and portal

it already supports returning arrays of things from render, which is essentially fragment

cool, just got home, gonna give a try to the RC and see if everything goes smooth

great

give a round across many different components, didn't find any issues so far 🙂

all the previous issues I found are gone

about the fragments, so you are saying that if I'm using React 16, I can return a vector from the render function, and that is the same as returning a fragment?

Fragment lets you do a little more, but yes, you can return an array from render

https://pawelgrzybek.com/return-multiple-elements-from-a-component-with-react-16/

2.6.0-RC2 released with support for React fragments and returning vectors of children from defsc

book updated

@wilkerlucio so it turned out I didn’t realize the spec for defsc would not allow a vector. Fixed that..hopefully that does not cause any defsc problems. fragment is now part of all dom namespaces.

@tony.kay nice, but I think frament is more primitives thing than a dom thing

considering that fragments will work in RN or other React environments, its not a DOM specific thing

feel free to patch and PR as long as it’s tested in the envs it is intended to work.

ok, I think I'll have some time for that later

thx. Did you think fragment would just work in native (e.g. createElement React.Fragment)?

I don’t use native, so I don’t know

if not, perhaps we should create a native ns for things that help there

I think so, considering its from the React package, not from ReactDOM

yeah, I just don’t have time to test out native stuff

got some reason I don’t seem to be getting proper blur events either in react 16 or the new Fulcro…

hm…think it might be a problem with a js ecosystem component, actually

or the new lifecycle wrappers in Fulcro. Be interested in hearing other’s reports of lifecycle weirdness with this RC