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
fix(nuxt): handle optional params within a path segment #23070
Conversation
Run & review this pull request in StackBlitz Codeflow. |
test/basic.test.ts
Outdated
@@ -205,6 +205,42 @@ describe('pages', () => { | |||
await expectNoClientErrors('/?test=true') | |||
}) | |||
|
|||
it('/optional/[[opt]].vue', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead, would you update packages/nuxt/test/pages.test.ts
? I think we can cover this in a unit test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added unit tests. Do you insist to replace fixtures/basic
ones? They also checks the ordering of routes as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you β€οΈ
I think the route ordering should be tested by vue-router rather than us. The e2e tests here are good but I think we can save the CI time.
π Linked issue
resolves #23069
β Type of change
π Description
π Checklist