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

Switch to using @react-spring/web internally to solve deprecation warnings #37

Open
Macil opened this issue Feb 3, 2020 · 0 comments
Open

Comments

@Macil
Copy link
Collaborator

Macil commented Feb 3, 2020

This project uses react-motion internally, which doesn't appear to be very maintained. We get console warnings from modern versions of React because react-motion uses deprecated React features.

The library react-spring seems very similar to react-motion and better maintained, so I plan on switching this project to using it. I'm just opening this issue here as a todo item for myself.

The main consequence to users of react-draggable-list would be that the value of the springConfig prop will be replaced with a react-spring config object, so this change would be paired with a major version bump.

@Macil Macil changed the title Switch to using react-spring internally Switch to using react-spring internally to solve deprecation warnings Feb 15, 2022
@wegry wegry changed the title Switch to using react-spring internally to solve deprecation warnings Switch to using @react-spring/web internally to solve deprecation warnings Dec 7, 2023
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

1 participant