Should the type of $route.query.xx be unified into a String type?

[zhangzhengyi12]

What problem does this feature solve?

If I use

this.$router.push({
      name: 'pageB',
      query: {
        money: 100, // number
      }
 })

jump to pageB

now

// pageB
export default {
  mounted(){
     console.log(typeof this.$route.query.money)
     // case1 If the page enters as push, then the output is [number]
     // case2 If this page B is refreshed, then the output is [string]
  }
}

Since the requery type cannot be retrieved from the current URL when re-entering the page，
So should the type of the unified parameter always be string to avoid some unnecessary type problems?

using Google Translate Thanks

What does the proposed API look like?

Uniform parameter type is String

[posva]

IMO yes, they should always be casted to strings to make things consistent

[tesla3327]

Related to #2131

[posva]

Let's close this in favour of #2131 . We should allow numbers and string for convenience but cast things to strings for consistency