useTrail should follow the same API structure as useTransition
Open
Nobody has claimed this yet.
kind: request
- Dominant language
- TypeScript
- Stars
- 29.1k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
🚀 Feature Proposal
In the title.
Motivation
Cause it makes no sense why it wouldn't?
Example
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 comparing the documented or exposed APIs of useTrail and useTransition, then review the linked CodeSandbox example to identify the intended structure. Done means useTrail follows the same API shape as useTransition without losing its existing behavior; the issue does not name implementation files or tests.
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
- Needs clarification
- Newbie friendliness
- 25/100