Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Components manually imported via $options.components do not exist when mounted() #1067

Closed
reginsmol opened this issue Dec 13, 2018 · 1 comment
Closed

Components manually imported via $options.components do not exist when mounted() #1067

reginsmol opened this issue Dec 13, 2018 · 1 comment
Labels
bug

Comments

@reginsmol
Copy link

reginsmol commented Dec 13, 2018 •
edited
Loading

Version

1.0.0-beta.27

Reproduction link

https://github.com/Reginsmol/test-utils-components-option-reproduction

Steps to reproduce

  • npm install
  • npm run dev
  • npm run unit

What is expected?

It should print out the ChildComponents in the components option.

What is actually happening?

it only contains "transition" and "transition-group" when doing a regular mount(), however using shallowMount() the child components (ChildComponent, ChildComponent2) exist in the object.
@reginsmol reginsmol changed the title Components manually imported via $options.component do not exist when mounted() Components manually imported via $options.components do not exist when mounted() Dec 13, 2018
@eddyerburgh eddyerburgh mentioned this issue Dec 29, 2018
Closed
@reginsmol
Copy link
Author

Is there any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reginsmol @eddyerburgh