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
type OptionsItem = { label: string; value: string; disabled?: boolean };
Describe your issue here.
now,optionitem support string value,but sometimes the system developed surply number value of optionitem.
type OptionsItem = { label: string; value: string|number; disabled?: boolean };
Problem
but if change here,and change the api and mock interface to support number value,the console will get a warn info,as:
[Vue warn]: Invalid prop: type check failed for prop "value". Expected String with value "1", got Number with value 1.
runtime-dom.esm-bundler.c8ed2c92.js:1181
If the feature requests relates to a problem, please describe the problem you are trying to solve here.
Expected behaviour
What should happen? Please describe the desired behaviour.
Alternatives
What are the alternative solutions? Please describe what else you have considered?
The text was updated successfully, but these errors were encountered:
Subject of the feature
type OptionsItem = { label: string; value: string; disabled?: boolean };
Describe your issue here.
now,optionitem support string value,but sometimes the system developed surply number value of optionitem.
type OptionsItem = { label: string; value: string|number; disabled?: boolean };
Problem
but if change here,and change the api and mock interface to support number value,the console will get a warn info,as:
[Vue warn]: Invalid prop: type check failed for prop "value". Expected String with value "1", got Number with value 1.
runtime-dom.esm-bundler.c8ed2c92.js:1181
If the feature requests relates to a problem, please describe the problem you are trying to solve here.
Expected behaviour
What should happen? Please describe the desired behaviour.
Alternatives
What are the alternative solutions? Please describe what else you have considered?
The text was updated successfully, but these errors were encountered: