feat(pages)!: explicitly allow optional params with [[

[danielroe]

Resolvesnuxt/nuxt#13408. Also see nuxt/nuxt#13788.

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Currently routes ending in a dynamic param are marked as optional, e.g.: ~/pages/[slug].vue.

This PR instead requires double bracket syntax to enable optional params: e.g. ~/pages/[[slug]].vue. (This also means you can enable optional parameters earlier in the path.)

👉 Migration

If you are relying on [slug] at the end of a route to generate an optional parameter, you will need to rewrite it as [[slug]].

[netlify]

✅ Deploy Preview for nuxt3-docs ready!

Name	Link
🔨 Latest commit	bbc3493
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/62680dfc4aaee0000827606a
😎 Deploy Preview	https://deploy-preview-4537--nuxt3-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[pi0]

This seems a good change but I guess it is not completely resolving nuxt/nuxt#13408 considering we might have more than one optional param in the path...

(Side note: Both server routes and vue-router does not have this consideration that "last dynamic segment is necessarily optional". i was unaware even we were doing this!)

[danielroe]

@pi0 How about we change the default to non-optional at end of route, and use double brackets - e.g. [[slug]] - to indicate optionality, which can apply to any level in path?

[pi0]

Double bracket seems a nice idea!

[atinux]

I love this idea!

[atinux]

Happy to merge once the documentation is updated. Any blockers @pi0 ?