# Form Handling

When using Kdux in strict mode, it could be a bit tricky to use k-model on a piece of state that belongs to Kdux:

<input k-model="obj.message">

Assuming obj is a computed property that returns an Object from the store, the k-model here will attempt to directly mutate obj.message when the user types in the input. In strict mode, this will result in an error because the mutation is not performed inside an explicit Kdux mutation handler.

The "Kdux way" to deal with it is binding the <input>'s value and call a method on the input or change event:

<input :value="message" @input="updateMessage">

// ...
computed: {
  ...mapState({
    message: state => state.obj.message
  })
},
methods: {
  updateMessage (e) {
    this.$store.commit('updateMessage', e.target.value)
  }
}

And here's the mutation handler:

// ...
mutations: {
  updateMessage (state, message) {
    state.obj.message = message
  }
}

# Two-way Computed Property

Admittedly, the above is quite a bit more verbose than k-model + local state, and we lose some of the useful features from k-model as well. An alternative approach is using a two-way computed property with a setter:

<input k-model="message">

// ...
computed: {
  message: {
    get () {
      return this.$store.state.obj.message
    },
    set (value) {
      this.$store.commit('updateMessage', value)
    }
  }
}