2 ms·

I haven't looked at ReactReason beyond seeing it mentioned in a few conference slides. The new context API (`React.createContext`) is intended to be stable goi

I haven't looked at ReactReason beyond seeing it mentioned in a few conference slides. The new context API (`React.createContext`) is intended to be stable going forward. As far as I know, the only potential "unstable" aspect remaining is the `changedBits` prop for potentially optimizing which consumers actually update on a given context value change. So no, I don't have any particular reservations at the moment. Legacy context still works but is very deprecated, and new context allows us to refactor the internals in a way that's ultimately simpler and hopefully more compatible with where React is going. Can you point me to some of these ReactReason discussions?

hajile 8y ago
https://github.com/reasonml/reason-react/issues/199#issuecomment-404705135 https://github.com/reasonml/reason-react/issues/199#issuecom... It's one of the big reasons our company isn't even considering ReactReason at present. Lack of support for version 16 APIs is killer when you already have stuff depending on them.
- acemarke 8y ago
  Huh. I'm very surprised to see that comment coming from Cheng Lou. React 16.3 came out in March, and the React team has been encouraging everyone to use the new context API since then. Really not sure what's behind his comment.