react-component / react-component/motion
State not always up to date
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 178
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am trying to trace the root cause of https://github.com/ant-design/ant-design/issues/38818 ,
and I believe this is related to rc-motion, either being buggy on react-18, or maybe misused.
Here is a sandbox where I can repo the issue
https://codesandbox.io/s/small-moon-nigikp?file=/src/App.js
https://user-images.githubusercontent.com/1194083/203934195-bbaab64f-fd94-44c8-9b66-c292e4e6ceed.mov
as you can see, the element does not seems to end up in the state it is supposed to be, as sometimes Parent is hovered, but child is not visible
Contributor guide
No contributing guide indexed for this repository
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 with the linked CodeSandbox at src/App.js and reproduce the behavior under React 18. Trace how rc-motion handles the Parent hover and child visibility transitions; done means the element consistently reaches its expected state and the reproduced case no longer shows Parent hovered while the child is hidden.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100