Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1.4k
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
Hello I'd like to know if I'm reading the docs correctly regardingpathless layout routes andpathless route group directories. This is something that has been asked about multiple times with zero clarification. See similar discussions:#4975,#4319,#3837. ExampleBelow is a screenshot of a mock routing structure. The application is grouped as:
![]() ![]() Note that in this example, the Required behaviourEach group will have it's own layout file which provides1) a Obtaining the required behaviourAccording to the docs regardling pathless layouts and pathless route groups, to get this expected behaviour, I would need to use a pathless layout structure, e.g., Where each set of pages has it's own pathless layout file at the My confusionHowever, the example above using pathless route groups with a nested The docs clearly state the following regarding pathless route group directories: If they (to my knowledge) both work the same,1) why do the docs not reflect this?2) what's the point in supporting both methods? Any light shed on this would be great. I'm pleased that I can get the expected behaviour using route groups as I do quite like the NextJS file routing, but I'm very confused as to why the docs urge you towards using pathless layout routes. Edit: there's prior discussion where@schiller-manuel also indicates that route groups are again,purely organisational, and do not influence anything. Edit: included a devtools screenshot for additional context. TIA |
BetaWas this translation helpful?Give feedback.

