React 16 support

[MickeyKay]

Any plans to upgrade support for React 16? We're upgrading all the apps in our org, and will likely need to fork Kasia to do so. Anything in the works on this front that we can collaborate on? If not, we'll move ahead on our end and reach back out when we're complete. Thanks!

[sdgluck]

Thanks for raising this.

There aren't any upgrade plans in progress/the pipeline currently. We have stalled on v5 due to other priorities, however I would love to see it completed and released this side of 2019.

What is necessary for React 16 support? Perhaps there is some work that can be done on the v5 branch that would mean a single major version release could support React 16 and include the other pending features/bug fixes?

You can see the progress of v5 here: https://github.com/outlandishideas/kasia/compare/v5.0.0

[joshlevinson]

@sdgluck do you have a 5.0.0 roadmap?

[sdgluck]

@joshlevinson Sorry, I missed your comment.

This is just copied from the changelog on v5 branch. Some of these are incomplete, which I have marked with a star.

• [BREAKING] Improved preloader API (runSagas has become runPreloaders, see docs)
• [BREAKING] Actions (e.g. createPostRequest/createQueryRequest) signature changed to take single object as argument
• Option to preserve return value of connectWpQuery query function (#30)
• Support comma-separated dot-paths for shouldUpdate (#38)
• Support generator query functions (!59)
• Support for per-component naive caching strategies (browser) (#74) *
• Access to req and res objects in query functions (SSR) (#77)
• Added prettier-standard via husky & lint-staged

So I guess we can add React 16 to that list, and I would also like to upgrade the build tooling to Babel 7.

Do you have any update on your experience moving Kasia to React 16?