Eduardo San Martin Morote
Eduardo San Martin Morote
I added a test but that seems to be working. If that's not what you meant a boiled down reproduction or a failing test would help. I updated the docs...
Ah I see, the behavior should be consistent: - `router.push({ name: 'optional', params: { p: null }})` - `router.push({ params: { p: null }})` No matter the current location. The...
> I'm not clear whether this is documented anywhere, but I think it's a reasonable assumption and something that people are likely to be relying upon, even though they may...
Thanks for the info, if you create a boiled down repro without external deps that would be really helpful
Yes, a reproduction without i18n and Nuxt would help. The repro with i18n still looks like a black box without any errors so I can't know what is happening
I reverted this and released a new patch
The inconsistency in `route.fullPath` is a bit inconvenient but as long as the `route.hash` (and the other properties) is consistent, it's okay. In future major versions it will be possible...
I had to revert this because it breaks other behaviors... This will be a wontfix until we use URL
Thanks for the investigation. It would be interesting to see an actual perf benchmark (without nuxt). The difference in creation shouldn't be that big. That said, Vue Router 3 had...
I checked on https://lahmatiy.github.io/cpupro/ with the cpuprofile file and the insertMatcher is what takes the most time! Feel free to give the topic some thought and try to raise a...