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
[MdBottomBar] Missing required prop: "to" found in md-bottom-bar-item #1237
Comments
Could you reproduce it on Codepen? |
@CocoChen917 Looks like you using older version where prop |
I encounter the same problem with project init by vue-cli script: // app.vue
<template>
<div id="app">
<router-view />
<md-bottom-bar >
<md-bottom-bar-item :to="'/home'" md-label="Home" md-icon="home"></md-bottom-bar-item>
<md-bottom-bar-item :to="'/issue'" md-label="Issue" md-icon="favorite"></md-bottom-bar-item>
</md-bottom-bar>
</div>
</template> // router
export default new Router({
mode: 'history',
routes: [
{
path: '/home',
name: 'home',
component: Home
},
{
path: '/issue',
name: 'issue',
component: Issue
}
]
}) I start a minimalist project with this part only, but problem is still there.
after that, items can also active or unactive when click, but the address in browser has no change,and throw this [Vue warning] twice at every click is this a bug? what can I do |
@luob5 try removing binding put only |
@Samuell1 I've all tried, |
now I have to use <md-bottom-bar class="bottom-bar">
<router-link class="bottom-bar-item">
<md-bottom-bar-item>
</router-link>
...
</md-bottom-bar> .bottom-bar {
display: flex;
}
.bottom-bar-item {
flex-grow: 1;
}
.md-bottom-bar-item {
width: 100%;
} |
can you check your package-lock? @luob5 because this issue looks like for version 0.8.x |
"vue-material": {
"version": "1.0.0-beta-7",
"resolved": "http://registry.npm.taobao.org/vue-material/download/vue-material-1.0.0-beta-7.tgz",
"integrity": "sha1-zXu8kZ1LQ7cdkfr8m17a1Wvaoyc=",
"requires": {
"date-fns": "1.29.0",
"deepmerge": "2.0.1",
"fuzzysearch": "1.0.3",
"is-promise": "2.1.0",
"popper.js": "1.12.9",
"raf": "3.4.0",
"vue": "2.5.13",
"vue-ga": "1.0.0"
}
}, it's difficult for me to connect official npm (Great Firewall).
I'll try again CDN mode tomorrow, thanks |
official
|
+1 |
@Samuell1 +1 Bug is not fixed. Still present in 1.0.0-beta-8. |
@mahapo i cant reproduce it in our dev branch |
I tried |
I get the same issue, created vue project using vue-cli
|
@mahapo using version from dev branch doesnt change anything because we doesnt recompile it everytime |
This problem seems to have been fixed in 6860d3a However, it is not included in 1.0.0-beta-8, so I'm happy if you can merge it. |
This should be fixed in new version. https://github.com/vuematerial/vue-material/releases/tag/v1.0.0-beta-10 |
@Samuell1 The To get around this I just did this |
my vue version is 2.5.2, thanks~
The text was updated successfully, but these errors were encountered: