Accessing history
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 795
- Forks
- 55
- Avg merge
- 5h 5m
- Merged PRs (30d)
- 2
Description
We have an area where we want to include a button that navigates the users back to the previous context. The context here is not the page immediately before, but another area.
How is the best way to approach this use case? Is there any way to associate metadata (such as the context name related to a route) to the history and access them later?
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
The issue names no files, tests, or entry points. Start by reviewing the routing and history APIs used by the project, then clarify how route-associated context metadata should be stored and retrieved. Done should include an agreed approach for navigating to a prior context rather than merely the immediately preceding page.
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