Namespace conflict with Vuetify v-touch
See original GitHub issueHi! Vue-touch-events stopped working after I installed Vuetify (https://vuetifyjs.com/en/). I see that Vuetify also has a v-touch directive, https://vuetifyjs.com/en/api/v-touch/. This is probably why my vue-touch-events stopped working. How can I deal with this? I want to use vue-touch-events, since it has more options that Vuetify, but it seems to be overridden by Vuetify and no longer works. Anders
This is how I use vue-touch-events:
v-touch:swipe="swipeHandler"
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Developers - Namespace conflict with Vuetify v-touch - - Bountysource
Hi! Vue-touch-events stopped working after I installed Vuetify (https://vuetifyjs.com/en/). I see that Vuetify also has a v-touch directive, ...
Read more >vue2-touch-events - npm
Customize the directive names to avoid namespace conflict. By default, the touch means v-touch and v-touch-class are available, and you can use ...
Read more >Equal components that conflict with each other (VUETIFY)
solved by swapping bootstrap tabs for vuetify tabs.
Read more >vue2-touch-events: Versions | Openbase
Add new namespace parameter to solve conflict with vuetify.js; Update README ... but you must make sure your click events are binding with...
Read more >Touch directive - Vuetify
The v-touch directive allows you to capture swipe gestures and apply directional callbacks. # Usage. On a mobile device, try swiping in various...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Considering how few people should have to use the namespace option, I’m glad you’ve taken the easy way out. Not worth you making massive changes, especially when they have other solutions like using vuetify-loader to do treeshaking, which should be the preferred solution as vuetify is massive and no one uses all of it.
Is there any reason I can’t see anything about 3.2.0 here on github?
vue-touch-events has only one file
index.js
, you can copy this file to your project and change the directive name to others 🤔