It may be less useful to formalize a 'Form' component when a View may want inputs in a variety of contexts that do relate to each other.
Instead, since inputs should have a unique(-ish*) actionId, developers can specify for an input which inputs the values of which should be included in action handlers.
This implies (I think) a provider-scoped registry of input values.
(*): A developer could meaningfully have multiple inputs of the same actionId on the page as long as they are the same underlying type (though using potentially different interactive variants), and they should reflect that same underlying value.
It may be less useful to formalize a 'Form' component when a View may want inputs in a variety of contexts that do relate to each other.
Instead, since inputs should have a unique(-ish*)
actionId, developers can specify for an input which inputs the values of which should be included in action handlers.This implies (I think) a provider-scoped registry of input values.
(*): A developer could meaningfully have multiple inputs of the same
actionIdon the page as long as they are the same underlying type (though using potentially different interactive variants), and they should reflect that same underlying value.