Same routes shared across multiple tabs.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start by reviewing the route definitions and the tab and stack behavior shown in the issue, then trace how matching routes are selected during navigation. Done means common routes can be shared without copying them into every tab stack, while a matching route stays in the current tab and is pushed onto its stack.
Written by the indexing model from the issue text.
Description
I have a use case where there are many routes that are shared across multiple tab stacks.
Example:
<TabsRoute>
<StackRoute>
<IndexRoute path="/friends">
<Route path="/user/:userId">
<Route path="/user/:userId/followers">
</StackRoute>
<StackRoute>
<IndexRoute path="/me">
<Route path="/user/:userId">
<Route path="/user/:userId/followers">
</StackRoute>
</TabsRoute>
/friends shows list of friends.
/me shows my account.
/user/:userId shows a profile of a user.
/user/:userId/followers shows a list of followers for a user.
Note that user can navigate to user profile and user followers from both friends and me tab.
They also share the same url pattern.
Since all routes are pretty much somehow connected to each other (think of Facebook app), almost all routes can be accessed from any tab stacks.
Desired behavior would be not to jump around between tabs, but stay in the current one if there is a matching route under the current tab, then push the matching route to the current tab stack.
Also, it would be nice if it can be done without copying common routes to each tab stack.
- Dominant language
- JavaScript
- Stars
- 636
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from jmurzy/react-router-native
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 10/100
jmurzy/react-router-native#81 · 5 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
jmurzy/react-router-native#79 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
jmurzy/react-router-native#78 · 2 comments · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
All issues in jmurzy/react-router-native
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
keyxmakerx/Chronicle#2284 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
soroswap/token-list#125 ·
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EveryInc/compound-engineering-plugin#2085 ·
Maintainers usually reply within 1 day