q-select slots > itemEvents no longer exists in Qv2
See original GitHub issueHello, I am in the process of migrating an application made in Qv1 to Qv2, but I cannot find an alternative to itemEvents (Computed properties passed down to QItem).
Apparently it no longer exists on V2
example :
<q-select
v-model="client.rank"
emit-value
map-options
:options="optionsRank"
label="Rank"
label-color="primary"
option-label="label"
option-value="value"
>
<template #option="scope">
<q-item v-bind="scope.itemProps" v-on="scope.itemEvents">
<q-item-section avatar>
<q-icon :name="scope.opt.icon" />
</q-item-section>
<q-item-section>
<q-item-label v-text="scope.opt.label" />
</q-item-section>
</q-item>
</template>
</q-select>
the problem is here : <q-item v-bind=“scope.itemProps” v-on=“scope.itemEvents”>
i have this in debug console :
[Vue warn]: v-on with no argument expects an object value.
is it enough to remove it? since the code continue to work without this v-on…
Thank you in advance for your help.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Developers - q-select slots > itemEvents no longer exists in Qv2 -
Hello, I am in the process of migrating an application made in Qv1 to Qv2, but I cannot find an alternative to itemEvents...
Read more >Select | Quasar Framework
The QSelect Vue component has two types of selection - single or multiple. This component opens up a menu for the selection list...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
To be more clear, just remove the
v-on
.v-bind
will take care of everything.@eunjin0212 Remove
v-on="scope.itemEvents"
as its no longer needed.