title: Trouble with Vue.js v-model within Quasar q-select tag dynamically rendering computed properties
body: <p>I am working with Vue.js within the Quasar framework to develop a hybrid app. At one point, I have a somewhat large form that I have split into subcomponents to deal with sections of input, and I’m using two-way binding via the .sync modifier (<a href="https://v2.vuejs.org/v2/guide/components.html#sync-Modifier" rel="nofollow noreferrer">https://v2.vuejs.org/v2/guide/components.html#sync-Modifier</a>, available in Vue 2.3.0+) to handle the data. I am then using computed properties to get and set each value in the parent. For example:</p>
  <pre><code>parent: 
  //html template
  &lt;parent&gt;
    &lt;child :firstName.sync=&quot;required.firstName&quot;&gt;&lt;/child&gt;
  &lt;/parent&gt;
  
  child: 
  //js
  computed {
    sync_firstName: {
      get () {
        return this.firstName
      },
      set (val) {
        this.$emit('update:firstName', val)
       }
     }
   }
  </code></pre>
  <p>This works well when I hardcode the v-model directive, as in <code>&lt;input type=“text” v-model=“sync_firstName”/&gt;</code> . However, when I assign the v-model attribute with a v-for directive (using :key  and dynamically rendered :options), the model value is read but the computed property not accessed/evaluated, for instance:</p>
  <pre><code>&lt;div v-for=“option in data&gt;
    &lt;q-select v-model=“data[’name’]” :options=“data.options&quot;&gt;&lt;/q-select&gt;
  &lt;/div&gt;
  </code></pre>
  <p>According to the eslint plugin guide for v-model (<a href="https://github.com/vuejs/eslint-plugin-vue/blob/master/docs/rules/valid-v-model.md" rel="nofollow noreferrer">https://github.com/vuejs/eslint-plugin-vue/blob/master/docs/rules/valid-v-model.md</a>), it is possible to use v-for to establish v-model properties. In my case, rendering the data <code>{{ data.name }}</code> shows the correct value (<code>sync_firstName</code>) — but this property is not then being evaluated (though the options values are being correctly rendered). However, if I hardcode the computed property <code>&lt;q-select v-model=“sync_firstName”&gt;&lt;/q-select&gt;</code>, the field renders perfectly. What am I missing?</p>
  <p>Thanks!</p>