Oh, my bad(( That’s written on pink…Thank you! I could do without q-field actually but I found that in the new version Quasar generates a custom id on every q-input element, like ‘id="qf_3061d64c-aa2d-4392-7fcf-6e019645a100’. With the previous Quasar version I used to add my own Id property either to QField or QInput which was very convenient to run quick tests. Adding my own id to QInput won’t overwrite the one genetated by Quasar (but it for works for QField). So I assume it’s not a good idea to attempt to do so at all as Quasar needs its own generated ID for better control over components…
Slots are a mighty powerful part of Vue. You shouldn’t avoid them. You should embrace them, as they are often used in Quasar and give you the most flexibility. 😄
Thank you for your suggestions, I have tried them all well previously and now I found the issue was that I was using lazy model change with @change event and v-model at the same time. Lazy @change works only without v-model. However, I wanted to render some changes via v-model in real time (like values on q-range labels when moving the slider), and display some elements, like buttons, only on lazy model change. I wonder if such a combination is possible?
