Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade react version to remove unwanted warnings of findDomNode #71

Open
Atabic opened this issue Aug 4, 2022 · 3 comments
Open

Upgrade react version to remove unwanted warnings of findDomNode #71

Atabic opened this issue Aug 4, 2022 · 3 comments

Comments

@Atabic
Copy link

Atabic commented Aug 4, 2022

Hi v0ltoz,

Some people are using this library with a newer react version under strict mode and it is throwing a warning

react-dom.development.js:86 Warning: Legacy context API has been detected within a strict-mode tree. The old API will be supported in all 16.x releases, but applications using it should migrate to the new version. Please update the following components: FormControl. Learn more about this warning here: https://reactjs.org/link/legacy-context
react-dom.development.js:86 Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of DateTimeRangeContainer which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node

These are the two warnings. Link to StackOverflow issue is here

@mohsentaleb
Copy link

@Atabic
I made a fork which resolves this. It's built with React 18+ and Vitejs:
https://github.com/mohsentaleb/react-tailwindcss-datetimepicker

@paulgromy
Copy link

@mohsentaleb Can you tell me how can I use this library without tailwindcss? I would like to apply my styles.
The thing is, I'm using the "react-advanced-datetimerange-picker" library. But it has well-known problems. I'd like to keep my current styles but migrate to your fork. How can I do this?

@RoyalSoft-DevTeam
Copy link

Umm... Found same error in my side....
Without tailwindcss?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants