-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Directive doesn't register inside of <router-view>? #11
Comments
Can you tell me which dist are you using (1.x or 2.x)? and if you are using the latest version or not? I will setup a simple test and get back to you. |
Okay I just setup a small test and it appears its working properly, can you give a code snippet of your setup? |
Yeah Im confused... even with just: app.js:
routes.js:
app.vue:
forgot.vue
That's pretty much it... super stripped down example that still gives that warning |
You can close this... I havent figured it out, but theres a bigger problem with my setup, now its not recognizing my filters in the router-view either |
I lied, filter is fine, so maybe it is something weird. vue resource, vuestore, others work fine... just not vee validate |
Actually, as soon as I add the Vue.use(VeeValidate), my global filter stops working as well. My versions:
|
If you want I can email you my project so you can take a look? |
Here is my test setup: import Vue from 'vue';
import VueRouter from 'vue-router';
import VeeValidate from 'vee-validate';
import App from './App.vue';
import Foo from './Foo.vue';
import Bar from './Bar.vue';
Vue.use(VueRouter);
Vue.use(VeeValidate);
const router = new VueRouter();
router.map({
'/foo': {
component: Foo
},
'/bar': {
component: Bar
}
});
router.start(App, '#app'); Maybe something is wrong with your setup I'm not sure. or some conflict with the filter. sure you can email me: logaretm1@gmail.com |
Updated to Vue 2.0... directive errors gone, however now getting this when testing on an input: vee-validate.js?d4ab:993 Uncaught TypeError: Cannot read property 'dataset' of null |
the latest tagged version (2.0.0-beta.10) should fix this issue. can you confirm? |
All good now, thanks! |
I am having the same issue
when I try to use Vue.use(VeeValidate); I get the following |
I'm not sure if it is the same issue, can you create a new issue or add the entry point of your app, I don't think its caused by the |
Still not working with Vue 1.0. Any fixes? |
I'm having an issue... I register using Vue.use(VeeValidate)... If I look at the root component and my navbar component, i see the error object but on the router-view the error object does not exist and using v-validate gives a warning that the directive was not found.
Any thoughts?
The text was updated successfully, but these errors were encountered: