-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Regression: Pagination with [...page]
doesn't work at the "root level" (src/pages)
#4306
Comments
[...page]
doesn't work at the "root level"[...page]
doesn't work at the "root level" (src/pages)
[...page]
doesn't work at the "root level" (src/pages)[...page]
doesn't work at the "root level" (src/pages)
It was probably introduced in this PR: #4265 , checking now... |
I just noticed this is happening for me too ... |
Thanks! I'm going to assign this to @matthewp since his PR seemed to cause the regression. |
Reverting to [email protected] fixed this for me. Edit: Actually just saw this https://github.com/Coder-Spirit/coder-spirit.github.io/pull/4 and it's a better fix. Just add
|
Also, my guess it that this was already maybe broken before the PR that made no trailing slashes the default. So we might have to go back to the original |
Thanks for your patience, I'm looking into this issue now. |
What version of
astro
are you using?1.0.4, 1.0.5
Are you using an SSR adapter? If so, which one?
What package manager are you using?
yarn
What operating system are you using?
Linux (Ubuntu, x86_64)
Describe the Bug
When using the pattern
[...page].astro
inside the "root" directory (src/pages
), only the 2nd and following pages are generated, while the first one is discarded.Notes:
trailingSlash: 'always'
inastro.config.mjs
yarn dev
, only when looking at generated code viayarn build
.While we could use
index.astro
as a workaround, it can be quite cumbersome at the time of keeping track of pages.Link to Minimal Reproducible Example
https://stackblitz.com/github/castarco/astro_pagination_bug_example
Participation
The text was updated successfully, but these errors were encountered: