Current state: the relation control reads every item of the type it points at and
puts them all in a select. That suits the categories a site usually holds, and
stops suiting a type that grows large. The read gives up after ten thousand
items, and a plain select is hard to use well before that.
Proposal: give the control a search box that asks the server for matches instead
of loading the type up front. The listing endpoint already takes a search
parameter, so the work is a control that queries as the editor types and names a
held target without needing it in the loaded page.
Trigger: 0.5.0 ships relations, so the first site pointing a field at a type with
thousands of items meets a control that was built for tens.
Current state: the relation control reads every item of the type it points at and
puts them all in a select. That suits the categories a site usually holds, and
stops suiting a type that grows large. The read gives up after ten thousand
items, and a plain select is hard to use well before that.
Proposal: give the control a search box that asks the server for matches instead
of loading the type up front. The listing endpoint already takes a
searchparameter, so the work is a control that queries as the editor types and names a
held target without needing it in the loaded page.
Trigger: 0.5.0 ships relations, so the first site pointing a field at a type with
thousands of items meets a control that was built for tens.