-
-
Notifications
You must be signed in to change notification settings - Fork 605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken prev next from useContent, regression/breaking change #2338
Comments
Szymon-dziewonski
changed the title
Broken prev next from useContent, regression, breaking change
Broken prev next from useContent, regression/breaking change
Sep 24, 2023
This should be fixed in edge channel. Do you mind checking edge channel and confirm the fix? |
Hey @farnabaz seems like its fixed on edge channel indeed, so probably this ticket can be closed. Can you maybe point PR that fixes issue? |
I think those are the related PRs: |
@nobkd appreciate that :) Thanks |
Released in v2.8.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Darwin
v18.16.1
3.7.3
3.9.0
2.6.3
yarn@1.22.19
-
modules
,content
@nuxt/content@2.8.2
-
Reproduction
In 2.7.2
c91f92d4-2525-4e10-b20b-323dd0a7c99c.webm
Repo with reproduction
https://github.com/Szymon-dziewonski/NuxtContentPrefetch/tree/broken-pre-next
In 2.8.2 its broken totally (
next
andprev
method), around 2.7.4 starts breaking withprev
method only coming fromuseContent
60747c95-3b82-4ae0-af35-842b4bcb4a47.webm
Repo with reproduction
https://github.com/Szymon-dziewonski/NuxtContentPrefetch/tree/broken-prev-next-2.8.2
Both run
yarn
and thenyarn dev
, checkcontent
structure and runhttp://localhost:3000/1/1.1
then play with itDescribe the bug
When having nested structure like so:
There is breaking change or regression after version 2.7.2 that causes
prev
andnext
methods coming fromuseContent
not usable, pointing wrong next and previous linksAdditional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: