>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3577654. --> Reported by: [effulgentsia](https://www.drupal.org/user/78040) Related to !705 >>> <h3 id="overview">Overview</h3> <p>The <code>/canvas/api/v0/layout/*</code> route returns a <code>resolved</code> section within each component instance's <code>model</code>.</p> <p>This <code>resolved</code> data is also needed by API consumers other than Canvas UI, for example consumers of jsonapi endpoints or the API in <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/canvas/-/work_items/3575144" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/canvas/-/work_items/3575144</a></span>.</p> <p>An example for where that's needed is so that Canvas Workbench can show the images of components with image props. Just the media entity ID isn't enough for that.</p> <h3 id="proposed-resolution">Proposed resolution</h3> <p>Add <code>resolved</code> as a computed property of <code>ComponentTreeItem</code>, similar to how <code>processed</code> is a computed property of Drupal core's <code>TextItemBase</code>. That should be all that's needed to automatically expose it to GET APIs that normalize fields.</p> <h3 id="ui-changes">User interface changes</h3> > Related issue: [Issue #3577777](https://www.drupal.org/node/3577777) > Related issue: [Issue #3546597](https://www.drupal.org/node/3546597) > Related issue: [Issue #3571366](https://www.drupal.org/node/3571366) > Related issue: [Issue #3520449](https://www.drupal.org/node/3520449)