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…
M
Best posts made by mas
-
RE: q-field & q-input issue on v1.1.0
-
RE: can't access i18n translation inside vuex state.js file
I imported i18n in vuex modules where I need it this way:
import { i18n } from 'src/boot/i18n'
and then accessed i18n translations in my vuex actions this way:
let myMessage = i18n.t('messages.myMessage')
Works like magic.