You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe it's not a common practice in real world? Just like antd Input component https://next.antdv.com/components/input, if you don't pass value(v-model), the Input component will hold it's internal value. This means you can type any value without manually set v-model:value. But if using useVModel, you can't typing anything unless set v-model:value="xxx".
Suggested solution
If this feature is reasonable. Maybe we could add interanl option in useVModel options for compatibility.
Clear and concise description of the problem
#622
Currently
getValue
inuseVModel
will always return undefined when props[key] and defaultValue is undefinedvueuse/packages/core/useVModel/index.ts
Lines 113 to 116 in 1558cd2
Maybe it's not a common practice in real world? Just like antd Input component https://next.antdv.com/components/input, if you don't pass value(v-model), the Input component will hold it's internal value. This means you can type any value without manually set v-model:value. But if using
useVModel
, you can't typing anything unless set v-model:value="xxx".Suggested solution
If this feature is reasonable. Maybe we could add
interanl
option inuseVModel
options for compatibility.Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: