Open lackneets opened 5 years ago
This problem is still existing
A real reproduction is required.
Just want to highlight that this is still an existing issue.
you can reproduce if set vue-component to Map in Vuex =)
I recently had this issue, any updates so far?
Version
5.0.0-beta.4
Browser and OS info
Chrome 73.0.3683.75 / Windows 10
Steps to reproduce
Firstly, create a two-layer Vue app with
{app: Object}
as props in the component.Secondly, pass app itself as a prop such as
:app="this"
What is expected?
Those error messages should not be displayed, unless vue is not designed to pass any components as props
What is actually happening?
Finally, Select on the component in dev-tools, as a result, it will reports many errors for example:
Of course I know it's not a good idea to have a such high dependency between two components, actually, I am on a transition period of restructure vue components. I had searched for any discussion about passing component(instance) into props, unfortunately, I got no information of that