Why have ion events?

lhk · March 28, 2020, 7:21pm

I’m trying to figure out the roadblocks in using ionic with vue or preact.
From your ionic/vue codebase:

Create a wrapped input component that captures typical ionic input events
and emits core ones

ionic-team/ionic/blob/8a161f053fd252a4c87fb59ebd610e9090b0072c/vue/src/components/inputs.ts#L4


import Vue from 'vue';


/**
 * Create a wrapped input component that captures typical ionic input events
 * and emits core ones so v-model works.
 * @param {} name the vue name of the component
 * @param {*} coreTag the actual tag to render (such as ion-datetime)
 */
export function createInputComponent(name: string, coreTag: string, modelEvent = 'ionChange', valueProperty = 'value') {
  return Vue.component(name, {
    model: {
      event: modelEvent,
      prop: valueProperty
    },

Is there a reason (beside historical) to have your own event system?

It looks to me as if these custom events are basically the only thing that require special workarounds before using a framework with out-of-the-box support for web components (like preact or vue). Is that correct?

mhartington · March 30, 2020, 2:24pm

Please wait until we are ready to start up vue development again.
We are waiting until Vue 3 has shipped before working on it again.

As for events… we have our own events for a consistent behaviour across all frameworks/runtimes.