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.

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

[Bug Report] NavMenu broken in 1.4.0-beta.1 #5966

Closed
smares opened this issue Jul 20, 2017 · 3 comments
Closed

[Bug Report] NavMenu broken in 1.4.0-beta.1 #5966

smares opened this issue Jul 20, 2017 · 3 comments

Comments

@smares
Copy link
Contributor

smares commented Jul 20, 2017

Element UI version

1.4.0-beta.1

OS/Browsers version

Chrome Version 59.0.3071.115 (Official Build) (64-bit)

Vue version

2.4.1

Reproduction Link

https://jsfiddle.net/2fwn5qq1/

Steps to reproduce

Add a NavMenu element and open the page

What is Expected?

The NavMenu should appear

What is actually happening?

Errors "Avoid using non-primitive value as key, use string/number value instead." and "Error in created hook: "TypeError: Cannot read property 'addItem' of undefined"" displayed in the console and the NavMenu does not appear

@Leopoldthecoder
Copy link
Contributor

Thanks for your quick feedback.

In 1.4.0 we added a key, which is a Boolean, to Menu. That's why the warning comes out. It seems next Vue version will support Boolean typed keys: vuejs/vue#6127 , but still we'll convert it to a string/number.

@Leopoldthecoder
Copy link
Contributor

Oh, also this bug is related to vuejs/vue#6093

@Leopoldthecoder
Copy link
Contributor

Fixed in #5970

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants