Use plain string store for allowedTargets multiselect

[Copilot]

The linked review comment called out the allowedTargets Ext.ux.form.MultiSelect configuration in the link field editor. Its store was being passed as {text} objects instead of the plain string array expected by MultiSelect’s internal ArrayStore handling.

• Link field editor

  • Changed public/js/pimcore/object/classes/data/link.js to pass this.targets directly as the allowedTargets multiselect store.
  • Left the surrounding field configuration unchanged to keep the fix scoped to the reviewed line.

• Why this matters

  • Ext.ux.form.MultiSelect supports 1D arrays directly.
  • Using object entries here can break option rendering/selection because of how the component normalizes array-backed stores.

{
    xtype: "multiselect",
    name: "allowedTargets",
    id: "allowedTargets",
    store: this.targets,
    value: this.datax.allowedTargets,
    displayField: "text",
    valueField: "text"
}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud