Vue.js 2.0 support

I guess it going to be hard to do, but this is something necessary. 2.0 changes

No more .sync

My first analysis point to one real problem, the disappearance of .sync. so instead of:

:model.sync="model", :schema.sync="field"

We should do:

:model="model", :schema="field", @model-updated="modelUpdated", @schema-updated="schemaUpdated"

and inside the fields (abstractField.js)

props: ["model", "schema"],
watch: {
    model(newVal) {
        this.$emit('model-updated', newValue)
    },
    schema(newVal) {
        this.$emit('schema-updated', newValue)
    }
}

Also change formGenerator.vue:

watch: {
    // new model loaded
    model: function(newModel, oldModel) {
        if (oldModel == newModel) // model got a new property
            return;

        //console.log("Model changed!");
        if (this.options.validateAfterLoad === true && this.isNewModel !== true)
            this.validate();
        else
            this.clearValidationErrors();
    }
}

to

methods: {
    modelUpdated: function(newModel){
        if (this.model == newModel) // model got a new property
            return;

        //console.log("Model changed!");
        if (this.options.validateAfterLoad === true && this.isNewModel !== true)
            this.validate();
        else
            this.clearValidationErrors();
    }
}

This need to be tested.

Change in hook

Another thing could be related to ready becoming mounted. There’s no longer the guarantee to be in-document and could break most js dependent fields. We should test if the component is in document ourself now. I have no idea how to do that. Maybe check if vm.$el have a parent ? And if not use a small setTimeout to lauch the test again soon ?

---

I’m sure I’m missing a lot of problem, but this seem achievable. What are your thought ?

[icebob]

next branched merged to master. From now, master is for Vue 2.x, vue1 for Vue 1.x

[icebob]

I prefer to make a vue-next branch. The master stay for v1.x.x while the v2 implementation won’t be stable.