names conflict error

[l0rda]

Hello,

when i'm using 2 or more instances of one vue component with notifications block, i got error in console:

VueNotifications: names conflict - showMyCustomerError

[se-panfilov]

Hello, @l0rda
Thanks for your feedback.

To be honest, I'm not sure if I'm able to fix this issue in current version of vue-notifications.
Because by design vue-notifications shall be used on single-instanced components, such as "pages".

But I'll take a look if I can do something with it.

P.S. Right now I'm working on next iteration of vue-notifictions that won't have such problems. Would be smaller and much more straight forward.

P.P.S. Basically that error happens when component's instance already have method with such name ("showMyCustomerError" in your case). It's looks like vue-notifications tried to add same method for the component at least twice.

[dkcwd]

Hey @se-panfilov and @l0rda, just thought I'd share that I ran into the same thing and decided to use https://www.npmjs.com/package/vue-geb to centralise notification handling.

As an example of a quick implementation:

In your "main" page

  created: function () {
    // listen only to events emitted with the id 'vue-notification'
    this._notificationSub = this.$geb.getFilteredBus({id: 'vue-notification'}).subscribe(this.processNotification)
  },
  destroyed: function () {
    // avoid memory leaks by removing the subscription when destroyed
    if (this._notificationSub) {
      this._notificationSub.unsubscribe()
    }
  },
  methods: {
    processNotification: function (notificationData) {
      if (typeof notificationData.payload.type === 'string') {
        this[notificationData.payload.type]()
      }
    }
  },
  // register all the required notifications
  notifications: {
    showMyCustomError: {
      title: 'Failed',
      message: 'Failed to do the thing',
      type: 'error'
    }
  },

In a component within a method which should trigger a notification

  this.$geb.emit({id: 'vue-notification', payload: {type: 'showMyCustomError'}})

[azhard4int]

@se-panfilov any ETA for the next iteration release?

[se-panfilov]

@azhard4int and all other guys.

I'll try to release new version this weekend.
Sorry for delay, but I'm on the middle of job change right now.

Anyway, just to notice you - next release will be without backward compatability

[daniplaninc]

Hi, great library, been using it for a while now (+mini-toastr). No problem whatsoever, except the names conflict (I sometimes reuse the same vue components many times on the same page). Any ETA on the next version that would resolve this issue?

[se-panfilov]

@daniplaninc Can you provide an example?

Sorry I'm super busy, I've try to fix it today, but it's works for me (Basically this kind of errors should happens only if it clashes with methods names)

I mean that if you'll provide an example - it helps.

[daniplaninc]

Sorry for a delayed answer. This is not a breaking issue for me, as far as I know, the only thing that happens is the error message that appears in the console ("VueNotifications: names conflict - ). My application continues to work as expected.

As far as an example goes, maybe a description is enough. I have several global components defined (Vue.component(...)) and I use them repeatedly throughout my HTML, sometimes in a v-for. On page load, the error messages about duplication appear.

So basically whenever you will release a new version I will switch to get rid of the errors, but I am in no hurry.

[natali9t9]

I receive same error, @se-panfilov do you have any news ?

[CrixuAMG]

Any news?
The console is littered with errors: screenshot

[se-panfilov]

Fixed in release 0.8.1

[CrixuAMG]

That fixed it, thanks @se-panfilov!