Linking a `HostEntityUrlPropSource` to populate a `type: string, format: uri` in a `ContentTemplate` has no effect

Overview

UI bug with similar symptoms as 🐛 Some Linker choices have no effect Active and 🐛 Can't link field to non-required prop if it's empty on the entity. Active .

Happening for the new suggestion offered when editing component instances in a content template with a type: string, format: uri|uri-reference prop shape, since ✨ In a content template, how can I link to an entity? Active .

Reproduce by instantiating a my-hero test SDC in a ContentTemplate.

The child issues of 🌱 [META] Content templates Active that built the "select a suggestion from the server-side provided list of suggestions" specifically was designed to have the client side treat the suggested sources as opaque JSON objects (see #/components/schemas/StructuredDataForPropShapeHierarchicalSuggestionPathWithChoice in /openapi.yml). Apparently the /ui code does not do that, it actually parses it into client-side representations of DynamicPropSources — PropLinker.tsx does things like

    const fieldSource = selectedModel.source[propName] as DynamicPropSource;
    currentExpression = fieldSource.expression;

and

const isActive = item.source?.expression === currentExpression;

But it should not introspect source at all — if it didn't, this bug report would've been avoided. 📌 Follow-up for #3541037: Improve how list of field suggestions is displayed in the UI for `ContentTemplates` Active seems to have introduced this.

Proposed resolution

TBD

User interface changes