motiondivision / motiondivision/motion
[BUG] Components wrapped in `motion` don't pass props starting with "drag"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33.7k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 14
Description
1. Read the FAQs 👇
2. Describe the bug
When wrapping a component in motion, it causes props starting with drag to not be passed to the underlying wrapped component.
3. IMPORTANT: Provide a CodeSandbox reproduction of the bug
Codesandbox repro
4. Steps to reproduce
Steps to reproduce the behavior:
- Go to repro
- See that prop starting with
dragisn't being passed to wrapped component
5. Expected behavior
For props that start with drag to get passed to wrapped components
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 with the linked CodeSandbox reproduction and trace how the motion wrapper filters props before they reach the wrapped component. Verify the behavior with a prop whose name starts with drag; the issue is done when such props are passed through to the underlying component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100