Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Multi-level routing does not work under next.js

See original GitHub issue

Describe the bug Due to the way next.js routing is setup: [resource]->[action]->[id], multi-level routing breaks when trying to access a resource under a parent resource

To Reproduce Steps to reproduce the behavior:

Clone and run yarn dev on https://github.com/smparekh/refine-test
Click on ‘CMS’
Click on ‘Posts’
Posts will not be displayed as expected

Expected behavior When routing to a resource under a parentResource it should still handle it the same way as a top-level menu item

Screenshots WITH POSTS UNDER CMS:

WITH POSTS AT TOPLEVEL: Screen Shot 2022-04-12 at 18 50 35

Desktop (please complete the following information):

OS: macOS
Browser: Firefox
Version:
Used: supabase, next.js, antd, custom layout

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Used dataProvider [e.g. custom, Strapi, Airtable]

Additional context

@pankod/refine-antd@3.12.2
│  ├─ @ant-design/icons@^4.5.0
│  ├─ @pankod/refine-core@^3.12.1
│  ├─ antd@^4.17.1
│  ├─ dayjs@^1.10.7
│  ├─ react-markdown@^6.0.1
│  ├─ react-query@^3.19.2
│  ├─ remark-gfm@^1.0.0
│  ├─ sunflower-antd@1.0.0-beta.3
│  └─ tslib@^2.3.1
├─ @pankod/refine-core@3.12.1
│  ├─ export-to-csv-fix-source-map@^0.2.1
│  ├─ humanize-string@^2.1.0
│  ├─ lodash-es@^4.17.21
│  ├─ lodash@^4.17.21
│  ├─ papaparse@^5.3.0
│  ├─ pluralize@^8.0.0
│  ├─ qs@^6.10.1
│  ├─ react-query@^3.19.2
│  └─ tslib@^2.3.1
├─ @pankod/refine-nextjs-router@3.12.1
│  ├─ @pankod/refine-core@^3.12.1
│  └─ qs@^6.10.1
├─ @pankod/refine-supabase@3.12.1
│  ├─ @pankod/refine-core@^3.12.1
│  └─ @supabase/supabase-js@^1.22.4

Issue Analytics

State:
Created a year ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

biskuvitcommented, Apr 15, 2022

Hey @smparekh, Thank you for reporting a bug. I fixed your issue. Can you try again?

0reactions

omeraplakcommented, Apr 15, 2022

@omeraplak - I can make the update to the document

@biskuvit - What was the update to? refine or superplate?

thanks

Hey @smparekh , We’ve updated superplate. Thank you!

Top Results From Across the Web

2 levels nested routing in nextjs - Stack Overflow

I want dynamic routing at two levels. E.g.: {siteroot}/dynamicPage; {siteroot}/dynamicUrlSection/dynamicPage. My folder structure is: / ...

How to implement redirects in Next.js - LogRocket Blog

Redirects enable users to transfer an executed URL to a new URL to reroute an incoming request from one path to another.

Routing: Introduction - Next.js

Next.js has a file-system based router built on the concept of pages. When a file is added to the pages directory, it's automatically...

Shallow Routing - Next.js

When shallow routing is used with middleware it will not ensure the new page matches the current page like previously done without middleware....

Advanced Features: Internationalized Routing - Next.js

js has built-in support for internationalized (i18n) routing since v10.0.0 . You can provide a list of locales, the default locale, and domain-specific...