You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we print out the params for each route we get:
/en/a - lang: "en", param1: "a" - correct
/en/a/b - lang: "en", param1: "a", param2: "b" - correct
/en/a/b/c - lang: "en", param1: "a", param2: "b", param3: "c" - correct
/a - param1: "a" - correct
/a/b - param1: "a", param2: "b" - correct
/a/b/c - param1: "a", param2: "c" - wrong, param2 should be b and param3 should be c
Describe the bug
Considering the following route path:
/[[lang=en]]/[param1=param1]/[param2]/[param3]
If we print out the
params
for each route we get:/en/a -
lang: "en", param1: "a"
- correct/en/a/b -
lang: "en", param1: "a", param2: "b"
- correct/en/a/b/c -
lang: "en", param1: "a", param2: "b", param3: "c"
- correct/a -
param1: "a"
- correct/a/b -
param1: "a", param2: "b"
- correct/a/b/c -
param1: "a", param2: "c"
- wrong,param2
should beb
andparam3
should bec
This bug did not exist in 1.3.8, I'm assuming it was caused by fix: successive optional route parameters can now be empty.
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-p8azya?file=README.md
Logs
No response
System Info
Severity
blocking an upgrade
Additional Information
No response
The text was updated successfully, but these errors were encountered: