Skip to content

fix(nuxt): use greedy catchall when /index is the last segment #31528

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

Merged
merged 1 commit into from
Mar 25, 2025

Conversation

danielroe
Copy link
Member

🔗 Linked issue

resolves nuxt-modules/i18n#3464

📚 Description

we don't want to apply the more narrow regexp when there is no following segment, but we neglected to check for /index as a segment (which we ignore) meaning the path matcher we created had too low of a priority

Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

coderabbitai bot commented Mar 25, 2025

Walkthrough

The changes update the route generation logic and extend the dynamic route configurations within the project. In the utility file, the condition for appending a subsequent segment to the route path now includes an additional check to ensure the segment is not equal to "index". This modification refines how route paths are constructed based on file segment names. In the test file, a new dynamic route is introduced, mapping the [...id]/index.vue file to a catch-all route pattern with the name "id" and a corresponding path pattern of /:id(.*)*. This new route entry, which features an empty children array, is added alongside an existing dynamic route configuration. No modifications were made to the declarations of exported or public entities.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/nuxt/src/pages/utils.ts (1)

142-142: Consider adding a comment to clarify this condition's purpose

This condition now checks that the next segment is not 'index' to determine whether to use a greedy catchall pattern. Adding a comment would help future developers understand why this special case exists.

-      const routePath = getRoutePath(tokens, segments[i + 1] !== undefined && segments[i + 1] !== 'index')
+      // Use greedy catchall pattern when `/index` is the last segment
+      const hasSucceedingNonIndexSegment = segments[i + 1] !== undefined && segments[i + 1] !== 'index'
+      const routePath = getRoutePath(tokens, hasSucceedingNonIndexSegment)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d7f5db9 and ac244f1.

⛔ Files ignored due to path filters (2)
  • packages/nuxt/test/__snapshots__/pages-override-meta-disabled.test.ts.snap is excluded by !**/*.snap
  • packages/nuxt/test/__snapshots__/pages-override-meta-enabled.test.ts.snap is excluded by !**/*.snap
📒 Files selected for processing (2)
  • packages/nuxt/src/pages/utils.ts (1 hunks)
  • packages/nuxt/test/pages.test.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build
  • GitHub Check: code
🔇 Additional comments (2)
packages/nuxt/test/pages.test.ts (2)

611-613: Good test case for the new functionality

This test case properly covers the specific scenario where a catchall route has an index file as the last segment, which is exactly what the PR aims to fix.


616-622: Correct expected output with greedy catchall pattern

The expected output correctly verifies that the greedy catchall pattern (/:id(.*)*) is used when /index is the last segment in a catchall route path, which aligns with the PR objective.

Copy link

pkg-pr-new bot commented Mar 25, 2025

Open in Stackblitz

@nuxt/kit

npm i https://pkg.pr.new/@nuxt/kit@31528

nuxt

npm i https://pkg.pr.new/nuxt@31528

@nuxt/schema

npm i https://pkg.pr.new/@nuxt/schema@31528

@nuxt/rspack-builder

npm i https://pkg.pr.new/@nuxt/rspack-builder@31528

@nuxt/vite-builder

npm i https://pkg.pr.new/@nuxt/vite-builder@31528

@nuxt/webpack-builder

npm i https://pkg.pr.new/@nuxt/webpack-builder@31528

commit: ac244f1

Copy link

codspeed-hq bot commented Mar 25, 2025

CodSpeed Performance Report

Merging #31528 will not alter performance

Comparing fix/index-segment (ac244f1) with main (d7f5db9)

Summary

✅ 10 untouched benchmarks

@danielroe danielroe merged commit c89e603 into main Mar 25, 2025
45 checks passed
@danielroe danielroe deleted the fix/index-segment branch March 25, 2025 12:10
@github-actions github-actions bot mentioned this pull request Mar 25, 2025
@john-psina
Copy link
Contributor

@danielroe Thank you for the fix! I have a couple of questions regarding the availability of these changes:

  1. Will these changes be released only with Nuxt 4, or can we expect them in the next Nuxt 3 release?

  2. Is there any way to use this fix before the official release? I'm wondering if it's possible to install a pre-release version with this fix from the main branch for local development until the changes are officially released.

This would be really helpful for our current development process, as we're actively working with dynamic routes and i18n.

@danielroe
Copy link
Member Author

you can expect a patch release this weekend, and before then (once this is cherry picked to 3.x) you can use the nightly channel: https://nuxt.com/docs/guide/going-further/nightly-release-channel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect Route Resolution with Dynamic Routes
3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy