4.0 beta 2 - Two nestable components breaks repeater if using dynamic data in repeater

[wplit]

This is in related to API components, I made a quick fork of Elijah's example plugin, which is needed so there's two nestable components instead of one - https://github.com/wplit/example-oxygen-api-plugin

What happens is.. if there are two nestable elements in a template, and a page uses that template and adds a repeater.. when the user adds dynamic data to the repeater there is an error. "TypeError: Cannot read properties of undefined (reading 'name')" and that element becomes uneditable.

Here's a sandbox site showing the issue with a loom video just showing the error happening..

Username: admin password: 7oK)mseRdCZg@rox617%#aZR https://oxygen-qrawrrxkmxnll.oxygen-demo.qsandbox.me/

video following the steps and showing the issue - https://www.loom.com/share/a609f3967f084121ab78e23a13316e3a

Exact steps to reproduce..

• insteall that fork of the API components plugin, so there's two nestable elements.
• create a main catch-all template with an inner content element.
• create a new page, inheriting that template, and edit in Oxygen.
• Add a repeater with a custom query and an element to use dynamic data. eg a heading to use for the post title.
• Save and then go back to the catch all template.
• Nest two of the nestable components either before or after the inner content.
• Go back to the page with the repeater and try to select/edit the heading. It won't be editable and there should be errors in the console.

[wplit]

Update - the issue only shows up if using repeater in normal mode, not single mode.

Also, changing the nestable component to be a reusable template prevents it also.

Lastly, visiting the page with just ?ct_builder=true (instead of ?ct_builder=true&ct_inner=true) to prevent the inheriting template from being shown, also prevents it.

I'll sneak a feature request in here as it's related.. why not have a setting where the 'edit with oxygen' button that only loads in the current page and none of the inherited templates. so it's never including the '&ct_inner=true', even if just for performance, where there's no need to keep loading up the entire site.

[KittenCodes]

@wplit Thank you for writing such easy to follow and concise bug reports. It really is appreciated.

Replicated and reported internally.