Work in Strict Mode to avoid hitting a wall in upcoming React versions

Do you want to request a feature or report a bug?

It’s a feature of sorts, more like making sure we can still use this by the end of 2019…

What’s the current behavior?

Rendering a calendar inside React’s <StrictMode> wrappers yields a ton of deprecation / unsafe pattern warnings in the console:

• Deprecated findDOMNode() usage (the modern Refs API should be used instead)
• Unsafe lifecyle methods (typically componentWillMount() and componentWillUpdate())

What’s the expected behavior?

The codebase should try and move to the newer, cleaner, safer accepted ways to achieve the same results, in order not to find itself stonewalled when some upcoming React 16.x version finally strips these, some of which have long been deprecated.

My OSS/PR queue is already quite full for the next few weeks but I might try and give it a go around late Feb / March if the regular maintainers can’t.

[justingrant]

Hi @avindra - Nope, I ended up rolling my own plain-JSX solution. My own implementation is limited and lacks most RBC features, but my app has pretty limited needs so it’s good enough for now. I may consider switching back to RBC later but for now I’ve moved on.

[justingrant]

FWIW, I’ve moved away from using react-big-calendar, partially for this reason.