Event names cannot contain dashes about ngvue

[pcable]

I'm also having this issue. The callback in your case is being registered as somethingHappened however vue lowercases all event name when its going to call the callback so it never finds it. I'm trying to create a patch

[nicolaspayot]

@erickwilder well, you can listen to v-on-something-happened on a <vue-component> tag if the event you emit is using camel case syntax:

this.$emit('somethingHappened')

We can change this behaviour to allow events to be emitted with kebab case syntax, however this would introduce a breaking change.

[erickwilder]

The problem is that it goes against Vue's recommendation of aways emitting events in kebab-case. In our codebase we try to normalize all events following that convention as well

[erickwilder]

By the way. Do we really need to introduce a breaking change? We could simply allow both

[nicolaspayot]

I guess we could allow both syntaxes for event names but it would register twice the event callback, for each event... It might bring unnecessary performance drawbacks for an app with lots of components, with lots of events. I'd rather introduce a breaking change.

[realmerx]

Hello, I also hit the same problem and there seems to be a fork with this fixed (did not test this but code seems good): pcable@9974801.

I think it would be possible to have kebab case by default and also introduce a setting that one could set to send events as camel case to reduce breaking change problems.

One hacky way to hack around this is to override $emit method when creating vue constructor function for component that would be used inside angularjs:

var VueCompConst2 = Vue.extend(Object.assign({}, vueComponent, {
    created: function() {
        this.oldEmit = this.$emit;
        this.$emit = function(eventName) {
            eventName = eventName.split('-').map((p, i) => (i > 0 ? p.charAt(0).toUpperCase() : p.charAt(0)) + p.slice(1)).join('')
            this.oldEmit(eventName);
        }
    }
}));

[nicolaspayot]

This pull request #83 should fix the issue. Please, feel free to review it 😉