solara.Select{Multiple} uses custom parameter names of values/all_values, when it might make more sense to use value and items.
For reference, consider the v-select widget:
items
Can be an array of objects or strings. By default objects should have title and value properties, and can optionally have a props property containing any VListItem props. Keys to use for these can be changed with the item-title, item-value, and item-props props.
This would be a breaking change, but I think it's worthwhile to adopt the standard naming conventions before more components are created
As a side note, it would also resolve the confusion between values vs. on_value (no s in the callback param) for SelectMultiple, so at least there is some precedent for this breaking change to provide internal consistency even in the current version
solara.Select{Multiple}uses custom parameter names ofvalues/all_values, when it might make more sense to usevalueanditems.For reference, consider the
v-selectwidget:This would be a breaking change, but I think it's worthwhile to adopt the standard naming conventions before more components are created
As a side note, it would also resolve the confusion between
valuesvs.on_value(nosin the callback param) forSelectMultiple, so at least there is some precedent for this breaking change to provide internal consistency even in the current version