video1.0<iframe src="https://www.loom.com/embed/e915bcae39f5473f8cf3bacf73de3ebd" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/e915bcae39f5473f8cf3bacf73de3ebd-6105164bc44e91c0.gif95.402This Loom explains the difference between a standard Autocomplete implementation and Autocomplete Lsquare, focusing on how both assume string inputs and require special handling for composite types. The speaker notes they added a string check because Autocomplete can provide a string when it does not find a result. To be conformant, they split the selected target into separate text and UID components, since Autocomplete only works with text and the result mapping uses text matching. They mention that the page options hash is from title to UID, and that if there is no match it may be null, but the updated setup works as expected.