Ionic-framework: bug: ionic vue router.go(n) does not work when n < -1

[NunoSav]

Bug Report

Ionic version:
[ ] 4.x
[x] 5.x

Current behavior:
Trying to go back 2 or more routes.

Expected behavior:
App navigates back X amount of routes as long as there's that many in the history stack

Steps to reproduce:
Related code:
https://github.com/NunoSav/ionic-vue3-router-go-back

Other information:
I also made a vue3+router sample that mirrors the one above but without Ionic in it to see if the issue was with vue-router itself, it wasn't. You can check it here https://github.com/NunoSav/vue3-router-go-back

Ionic info:

Ionic:

   Ionic CLI       : 6.12.2 (/Users/nur/.config/yarn/global/node_modules/@ionic/cli)
   Ionic Framework : @ionic/vue 5.5.0

Capacitor:

   Capacitor CLI   : 2.4.3
   @capacitor/core : 2.4.3

Utility:

   cordova-res (update available: 0.15.2) : 0.15.1
   native-run (update available: 1.2.2)   : 1.2.1

System:

   NodeJS : v12.16.3 (/usr/local/bin/node)
   npm    : 6.14.4
   OS     : macOS Big Sur

[liamdebeasi]

Thanks, I can reproduce this. When you do router.go(n) it looks like we ignore the n value and assume 1 page navigation.

[NunoSav]

Any chance to get a build with this fix and https://github.com/ionic-team/ionic-framework/issues/22540 ? 😛

[liamdebeasi]

https://github.com/ionic-team/ionic-framework/issues/22540 was already fixed and should be shipping out soon. I've assigned this one to a milestone so you can track our progress on the milestones page: https://github.com/ionic-team/ionic-framework/milestones. The milestone assignment is subject to change, but it should give you a rough idea of how close fixes are to shipping.