Config with useSpring

[gmenih]

I'm not sure if I'm missing something, but is there a way to set the config with useSpring?

I'm trying to set the ease and the duration of a transition with useSpring, but I can't find a way how to achieve this.

[drcmda]

sure, just dump all the props into it,

import * as easings from 'd3-ease'

useSpring({ ..., config: { duration: 3000, easing: easings.easeCubic } })

It basically follows Keyframes lead there: http://react-spring.surge.sh/keyframes It takes all the props that springs understand: from, to, delay, immediate, reverse, config, etc. All the props it doesn't know will be crammed into "to". The only distinction is, useSpring is native by default.

[gmenih]

@drcmda I know this is quite experimental, but there seems to be a bug with useSpring. When setting the value of any prop to 0, in combination with the duration config, it will not properly set the very last value of the prop (after the animation ends, it should set it to 0, but it's stuck on whatever value it was before it). It works for all other values I tested, and it most cases, using interpolation for this will fix the issue.

See here: https://codesandbox.io/s/ryp2kj73np

Click on the button, and see that whenever the value should be set to 0 it's stuck on some arbitrary value.

Actually, it might not be related to the duration config.. It's also happening without it. but it's not as visible, because it eases out 🤔

Also, the width is properly updated as well, but I'm trying to use it with scrollTop

[drcmda]

Interesting. Indeed the width seems to be ok, but innerText is one frame behind in both duration and spring settings. The box will make it easy to track, thanks! I'll notify you when it's fixed.

[drcmda]

Should be fixed. Almost a decade writing code and i still make stupid mistakes like this:

😓

[gmenih]

It fixes the issue with innerText, but I can still reproduce this when using scrollTop property.. It's not that big of a deal. as just interpolating it to string fixes the issue, but just thought you might want to know about it.

Here's an updated example of the issue: https://codesandbox.io/s/oj0jx0m809

I went ahead and opened a PR for this, if you want to merge it in. I followed what you changed in the image above :)

#312

[drcmda]

Oh my, it's the same issue, sorry. Thanks for the PR, made another patch release (6.1.8).

[gmenih]

Yep, working now 👌 Thanks for your time :)

Closing this now