<q-tabs :refs="$refs" v-model=“TARIFF”>
<q-tab v-for=“eachTariff in tariffs” :name="‘tab’+eachTariff.value" icon=“message” >
{{eachTariff.label}}
</q-tab>
</q-tabs>
<!-- Targets -->
<div v-for=“eachTariff in tariffs” :ref="‘tab’+eachTariff.value">
{{eachTariff.description}}
</div>

this markup creates tabs with correct labels = eachTariff.label but this tabs are not switchable

@rstoenescu
yes I see it. i tryed this example and it works very well. but i need dynamic tabs. can you explain me why my code nod works?

I try to output tariffs inside tabs component like this but unsuccessfully. Can you tell me where is my mistake please

<q-tabs :refs="$refs" v-model="TARIFF">
  <q-tab v-for="eachTariff in tariffs" :name="'tab'+eachTariff.value" icon="message" >
    {{eachTariff.label}}
  </q-tab>
</q-tabs>
<!-- Targets -->
<div v-for="eachTariff in tariffs" :ref="'tab'+eachTariff.value">
  {{eachTariff.description}}
</div>

hello!

i’ m moving my project from jquery-ui to vue and Quasar and can’t find equal functionality between autocompletes.

In jquery-ui autocomplete i could fetch [{id, value}, {id, value}] pairs from server, show text value to user. When user select some autocomplete option select event fired and i could get that hidden id and perform some operation. In quasar i can’t find select event and can’t understand how to get hidden metadata like option identificator when user select some option

Hello! Does anybody try vuetifyjs framework ? can you compare it with quasar

Hello! I think unit test is much more important then linting. Why do you skip Karma configuration in template. It is very complicated and I think many devs like to skip it)