Provide a way to disable warnings for "No match found" when testing

[cexbrayat]

What problem does this feature solve?

When adding tests to a component using the router, one might need to provide a mock router. I currently use:

const mockRouter = createRouter({ history: createWebHistory(), routes: [] });
describe('Navbar.vue', () => {
  test('should ...', () => {
    const navbar = mount(Navbar, {
      global: {
        plugins: [mockRouter],
        stubs: {
          RouterLink: RouterLinkStub
        }
      }
    });
    // ...
  });
});

It works perfectly, but the router emits a warning:

console.warn node_modules/vue-router/dist/vue-router.cjs.js:225
    [Vue Router warn]: No match found for location with path "/"

As most tests are using the same code, the warning is emitted a lot and pollutes the test output.

What does the proposed API look like?

Until VTU or the router itself provides built-in support for testing (if ever, see vuejs/test-utils#152 for curious readers), do you think we could guard this warning with a setting to hide it? I can open a PR if you provide some guidance (and think this is useful of course).

[posva]

I see how this can be annoying. I think it's better to remove it, like in Vue router 3. It can be added in user land with a beforeEach hook:

router.beforeEach((to, from, next) => {
  if (!to.matched.length) console.warn('no match')
  next()
})

[cexbrayat]

The user land solution is a nice workaround, but quite cumbersome to add to every test suite in a real project :)

I'm not sure I understood you correctly sorry: I think it's better to remove it -> do you want a PR removing the warning from the codebase?

Edit: the proper one is https://github.com/vuejs/vue-router-next/blob/e050abcf617f5e35e1f251a58f364bc1ee73f68a/src/router.ts#L263-L265

[posva]

I'm not sure I understood you correctly sorry: I think it's better to remove it -> do you want a PR removing the warning from the codebase

yes. The warning can be added in user land for specific projects. We could also disable it if __TEST__ is defined or something similar that is defined by VTU

[posva]

On a second thought, this will help beginners (by helping them to find typos in to props) much more than it will hurt advanced users (by flooding their console) and can be fixed by adding a match all route to the test environment:

{ path: '/:pathMatch(.*)', component: NotFound }

In the case of a fake router, this can be handled internally as well

[posva]

As talked previously, this is helping more people than it's hurting. It's a common mistake to do a typo and people not realizing it. In the case of tests, we will provide a mocked router anyway

[migken]

This warn is too stupid, please remove it.