-
Notifications
You must be signed in to change notification settings - Fork 69
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
Re-initialize after updating containers #3
Comments
You can put If you use a same bag, I think you don't have to set options again. The first argument for |
Currently I created an event in the main file, that I call from the component. I do get access to vue-dragula, but with the error below.
Maybe I should elaborate; see the HTML below.
So the v-dragula should automatically add new containers in this situation? Using |
It's a bug in the this.categories = []
this.$nextTick(function () {
this.categories = newCategories
}) |
Thanks for looking into this, I'll give the 'workaround' a try! |
Currently I'm settings options for vue-dragula in the ready callback of the main Vue file, like so:
But in another component, I have an update function for the categories, which requires me to re-initialize vue-dragula so new (or removed) containers are taken into account. In this case the categories are the bags/containers.
How can I access
Vue.vueDragula.options
inside of a components method?this
doesn't work, and I can't find anything related on Vue itself or vue-dragula.This is probably not really an issue, but maybe the docs can be updated if you know how to do something like this.
The text was updated successfully, but these errors were encountered: