So having a props section work for the provided component, or if not provided, then the built-in one, that makes sense to me. And it would apply to any prop, not just modelValue.
One problem that could arise is people passing in the props for an assumed built in component (Number, Radio), but then later we change what the default component is (Range, Dropdown), and that new component uses those same props in a different way. So may have unexpected, hard-to-track breaking changes in people's apps. But this also feels like an edge case.
Maybe one of these:
Putting it in the
props
section makes more sense to me, as today you would have to do this:So having a
props
section work for the provided component, or if not provided, then the built-in one, that makes sense to me. And it would apply to any prop, not justmodelValue
.One problem that could arise is people passing in the props for an assumed built in component (Number, Radio), but then later we change what the default component is (Range, Dropdown), and that new component uses those same props in a different way. So may have unexpected, hard-to-track breaking changes in people's apps. But this also feels like an edge case.