[feat]: Native ability to switch to a new "idle" (looped) animation after the first (entrance) animation completes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 29.1k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
A clear and concise description of what the feature is
I'd like to be able to add an "idle" animation, perhaps which accepts another useSpring-defined variable, or a from and to (or any other way which makes sense).
The idea would be to loop this animation once the initial "from" and "to" has completed.
Why should this feature be included?
Whether or not there is already a recommended way to go about doing this then it would be really great to see something like this in the examples section, since I imagine a lot of people would benefit from the ability to have their animations seamlessly transition from the "entrance" animation to an "idle" (looped) animation.
Please provide an example for how this would work
An "idle" animation (e.g. idle useSpring prop), perhaps which accepts another useSpring-defined variable, or a from and to (or any other way which makes sense).
Kindest Regards,
Jay
P.S. I have not been able to join via the Discord link, it might be worth creating a new invite link.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing useSpring API and the animation examples, especially how completion of the initial from/to animation is handled. Determine the supported API shape for a looped idle animation and define a representative entrance-to-idle example. Done means the behavior and API are implemented and the examples section demonstrates the seamless transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100