b-form-radio-group: Using numeric values results in invalid prop type
See original GitHub issueThis issue effects the latest version (1.0.0-beta.8/9), after the changes made to radio elements.
When supplying <b-form-radio-group> with an options array with numeric values, for example:
[
{ text: 'Last 7 days', value: 7 },
{ text: 'Last 14 days', value: 14 },
{ text: 'Last 30 days', value: 30 },
{ text: 'Last 90 days', value: 90 },
]
the b-form-radio-group Vue instance complains about an invalid type for prop “Checked”:
vue.runtime.esm.js:472 [Vue warn]: Invalid prop: type check failed for prop "checked". Expected String, Object, got Number.
found in
---> <BFormRadioGroup>
Switching the values to strings resolves the warning, as expected, but it should also be possible to use radios to select between numeric values.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:10 (5 by maintainers)
Top Results From Across the Web
How can I use multiple b-form-radio-group avoiding visual ...
Since both <b-form-radio-group> elements have the same name, "radio-options", visually they are treated like one group.
Read more >type check failed for prop "options". expected array, got object ...
Expected String, Number, Object, Boolean, got Array shows for the program below mention? html: ... Using numeric values results in invalid prop type#1088....
Read more >Form Radio | Components - BootstrapVue
Radios support values of many types, such as a string , boolean , number , or a plain object . Inline or stacked...
Read more >bootstrap-vue - UNPKG
1, {"version":3,"file":"bootstrap-vue.js","sources":["../src/utils/vue.js","../src/utils/env.js","../src/utils/warn.js",".
Read more >Form Radio | Components | BootstrapVue
Radio supports values of many types, such as a string , boolean , number , or an object . Inline or stacked radios....
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
We’re just finalizing the latest release (v1.0.0), so hopefully soon.
When fix for this issue will be on production ?