Replies: 4 comments
-
Hey! Thanks for opening the issue. The issue doesn't seem to contain a link to a repro (a snack.expo.io link or link to a GitHub repo under your username). Can you provide a minimal repro which demonstrates the issue? A repro will help us debug the issue faster. Please try to keep the repro as small as possible and make sure that we can run it without additional setup. |
Beta Was this translation helpful? Give feedback.
-
Couldn't find version numbers for the following packages in the issue:
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3. |
Beta Was this translation helpful? Give feedback.
-
@satya164 Happy to open a PR for this if you feel my case is valid and exporting this type adds value. |
Beta Was this translation helpful? Give feedback.
-
I want to avoid exporting it since there are already |
Beta Was this translation helpful? Give feedback.
-
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch
@react-navigation/routers@6.0.0-next.2
for the project I'm working on.I've been creating a custom tab bar and there was a requirement to add an action button that isn't a route. Mutating the original list that is in
state.routes
messes with the type inference and i was then required to manually set the types on the newly created list.Simply adding an export to the below type in the routers library allowed me more flexibility on adding items to the tab bar that aren't associated with any route and still keep the efficiency of iterating over state.routes to render out the other buttons.
Here is the diff that solved my problem:
This issue body was partially generated by patch-package.
Beta Was this translation helpful? Give feedback.
All reactions