search

vuejs / vue-class-component

ES / TypeScript decorator for class-style Vue components.
MIT License
5.81k stars 429 forks source link

Failed to resolve component #522

Closed Guervyl closed 3 years ago

Guervyl commented 3 years ago

Hi, I recently got a problem and I think it's a bug.

Here is link to reproduce the error: https://github.com/Guervyl/vuejs3-Failed-to-resolve-component.

I have a two components. Each has reference to the other. VueJs return a warning "Failed to resolve component". It shows the first component but, it did not show the inner component.

Here is the full warning so, that you can understand:

[Vue warn]: Failed to resolve component: Binding 
  at <ApiBinding> 
  at <Binding>
  at <App>

Binding has a component and ApiBinding has a component Binding.

The ApiBinding component will rendered if the user select to render it from the Binding component. And from the Binding component another ApiBinding component will be render if the user choose to render a new one. It's like a loop. And there is no problem with this logic because they depend to each other.

Why did I do it like that?

Imagine, in your code you want to make an Api (A) request. This Api request need a query parameter. This parameter, you want to fetch it from another Api (B). That api (B) needs a parameter value from another Api (C). This the logic of my vuejs components.

Guervyl commented 3 years ago

To reproduce it, clone the repo, install the dependencies and run the project. lick on the plus button and take look at the console. You should see the warning. I expected it to show new components.