vue 3 - channel callback contexts are broken due to relying on vm._uid

[tjk]

With multiple subscribed channels mounted at the same time, the contexts object (and other stuff) which relies on context._uid clashes which causes binding issues and maybe other things.

This seems to work as a stopgap, wasn't sure the best approach in the library to use...

import { getCurrentInstance } from 'vue'
/* ... */
app.mixin({
  created() {
    this._uid = getCurrentInstance().uid
  },
})

[mclintprojects]

This is happening in Vue 3.x, yes? @tjk

[tjk]

Yes, discovered this when I worked on a vue 3 migration. We've since started using @rails/actioncable directly so I can't say whether this is still the case, sorry. Feel free to close! (although given someone hearted the issue there is a chance it is affecting others?)

[iuri-gg]

having same issue - vue3 with action cable subscribing multiple times in different components causing issue. Any pointers how to resolve this?

[phlegx]

Can confirm problem!

[iaacosta]

Can also confirm the problem happens in Vue 3

This seems to work for me at the moment (thanks @tjk / @phlegx), you can also use create() but make sure the mixin is initialized before initializing the ActionCable plugin.

Haven't tried it in production yet, but if any confirmed related issues arise I'll be posting them here

[mclintprojects]

Fixed in v3