issue-249 feat: stub global components

[lmiller1990]

Maybe @cyberb can have some input here too.

This addresses #249

At the moment stubs will only work for locally registered components. For global ones (like <router-link>) you currently must registered a component globally to stub it, eg:

mount(Foo, {
  components: {
    RouterLink: {
     render() { return h('div') }
    }
  }     
})

Many people expect this to work (I also do)

mount(Foo, {
  global: {
    stubs: {
      RouterLink: {
       render() { return h('div') }
      }
    }
  }     
})

This PR takes anything from global.stubs and registers a global stub.

[cexbrayat]

I think it makes sense to move in that direction, it felt weird to write components: { RouterLink: RouterLinkStub } in tests 👍

That now leaves the question: do we need to keep components if we can do the same with stubs? But maybe we can't and I'm missing something.

[cexbrayat]

As I'm a bit unclear on how everything is related, can you maybe add a test where we try to find the component registered as a stub? I'd like to be sure that getComponent and friends work in that case as well.

I think a real use-case would be to stub RouterLink with RouterLinkStub, find it, and check its props to see if the component is creating links with the appropriate values. So I'd like to make sure we cover this 😅

[lmiller1990]

Good idea

[lmiller1990]

Done: 20c7694

Is this what you mean?

[cexbrayat]

Perfect, thanks Lachlan!

[lmiller1990]

Cool, want to give me a big old ✅

[lmiller1990]

@cexbrayat the global components option probably isn't really useful. That said, global is supposedmirro what you can do with app, eg app.component, app.mixin etc, so I think it's okay to have it. I don't expect people to use it, though (how often does someone register a global component? Only libs like Vuetify and that sort of thing, I guess).

[lmiller1990]

It is possible to use router-link <router-link /> (however unlikely)