> **Follow-up of** [!1112](https://git.drupalcode.org/project/canvas/-/merge_requests/1112) — see [note 1104077](https://git.drupalcode.org/project/canvas/-/merge_requests/1112#note_1104077). ### Overview !1112 merges the reference field's own field-level properties (e.g. an image reference's `alt`, `width`, `height`, `src`) together with the data of the entity it points to (e.g. that file/user entity's own fields) into a single object. A product manager needs to confirm this merged shape is the intended editor/component experience before it is relied upon. Concrete example of the produced shape, for a user's `user_picture`: ``` ℹ︎␜entity:user␝user_picture␞␟{alt↠alt,field_caption↝entity␜␜entity:file␝field_caption␞␟value,height↠height,src↠src,width↠width} ``` ```json { "__type": "user", "user_picture": { "alt": "Jane's avatar", "field_caption": "Jane at DrupalCon", "height": 200, "src": "/sites/default/files/styles/…/avatar.jpg", "width": 200 } } ``` Here `alt`, `height`, `src`, `width` come from the reference field's own properties, while `field_caption` comes from the referenced file entity. They are flattened into one object. ### Remaining tasks - Product manager confirms the merged shape (reference field properties + referenced entity fields in one object) is the desired behavior. - If not desired, open a follow-up to separate or restructure the two sources. ### User interface changes None unless the product decision requires reshaping the data.