Replies: 1 comment 3 replies
-
were you able to figure this out? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The file based routing hasn't exactly clicked all the way for me. The earlier NextJS
pages
file routing worked easily. I haven't made the conversion to Expo Route file based for some reason. Possibly because of the combo of Stacks & Tabs & Slots. I have been reading through the dynamic route docs. However, the documentation seems missing on how to navigate to a screen with a dynamic route, in terms of folder directory structure & slot v stack setupWhen I navigate to
/pattern/[id]
from within my tabs screen, something is getting lost in translation as Expo is not finding the route. I have tried all sorts of things, but I think it's related to my folder structuring.What I would like is: the destination
/pattern/[id]
to be a child of (tabs), not search.Here is my Tab's
_layout
:On my search UI, when I press on an item to navigate to,
The error from Expo is that the route cannot be found. You can see the
pattern
part of the route is not registering in the error:Here is my current sitemap from Expo:
I am asking for help on:
thank you in advance
Beta Was this translation helpful? Give feedback.
All reactions