Editing support for `type: array`: support multiple-cardinality Field Widgets (`StaticPropSource`s)
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3546869. -->
Reported by: [larowlan](https://www.drupal.org/user/395439)
Related to !681 !592 !725 !568 !81
>>>
<h3 id="overview">Overview</h3>
<p>In <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/canvas/-/work_items/3467870" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/canvas/-/work_items/3467870</a></span> support for shape matching on array was added.<br>
Unfortunately editing of those components doesn't work.<br>
It only ever saves the first value.<br>
I suspect this is because of the applied transforms.</p>
<h3>Manually testing</h3>
<p>Testing with any component that has "type: array" prop should work<br>
Try "Canvas test SDC for tags" provided by canvas_test_sdc test module<br>
If you add the component to the page, editing, and sorting do not work. If you add another item it may appear to work but if you reload the page the change will not save. Saving the page with the component will not work</p>
<h3 id="proposed-resolution">Proposed resolution</h3>
<p>Add support for editing.<br>
Add an e2e test to ensure it continues to work.</p>
<h3>Acceptance Criteria</h3>
<ul>
<li>A user can use a SDC component with a multivalue props.</li>
<li>Saving the values should work for multi valued props</li>
<li>Array items can be reordered within the props form UI</li>
<li>Once the code components have the ability of multi valued fields, this should work right out of the box, no new development will be needed.</li>
<li>Changes to array prop values are reflected in real-time preview</li>
<li>Array prop data is correctly saved and persisted when the page is saved</li>
<li>A site builder can define static array content directly in the builder without field mapping</li>
<li>Array props with validation errors display clear error messages to the user - If the errors do not show up correctly, we should spin up another ticket to fix that.</li>
</ul>
<h3 id="ui-changes">User interface changes</h3>
issue