HTTP API: new /xb/api/entity-form/{entity_type}/{entity}/{entity_form_mode} route to load form for editing entity fields (meta + non-meta)

Asked @lauriii for clarification at #3459234-10: [needs design] [research] Allow directly creating/editing entity title and meta fields → .

Wim Leers → credited lauriii → .

After discussing this in-depth with @lauriii, he is requesting this pivot:

8. As a content creator, I want to edit meta fields directly within the page builder interface. For example, the menu links and URL alias should be editable on the same page as the page builder.
9. As a content creator, I want to edit fields directly within the page builder interface. For example, the title should be editable on the same page as the page builder. I expect the page title to be displayed in the preview.

should both be covered by this; with the widgets for all of the entity fields (except for the XB field) appearing in the right sidebar, and hence in a single form. IOW: everything in the default form mode/display.

But the implementation should allow specifying a form mode, to allow in the future requesting only the meta fields (TBD how to identify these: 📌 [later phase] [RESEARCH] How to identify all meta fields for an arbitrary content entity? Active ), or only the "structured data" fields.

Shouldn't the url also include entity type and id?

Wim Leers → credited longwave → .

Is it possible to naively identify meta fields by finding all fields that are not displayed in any view mode? This probably doesn't hold true for all cases, but generally, if a field is never displayed it must be meta information of some kind?

— @longwave at #3463991-7: [later phase] [RESEARCH] How to identify all meta fields for an arbitrary content entity? → .

Let's use that heuristic in this initial implementation 👍

The MR so far adds the route and a controller that returns the form HTML wrapped in JSON.

I tried to start writing a test but I get a 404 from /xb/api/entity-form/node/1 and I'm not sure why.

got the test passing locally but looks I have update something for OpenApi spec to get the test to pass. Haven't had time to figure this yet

I think this is ready

A few questions about things that are unclear to me, but mostly requests for documenting the tricky things that you and @longwave identified/encountered :)

CI failed only due to 📌 Unbreak CI: #3458422 in Drupal 10.4 changed a method signature XB is overriding Active .

Automatically closed - issue fixed for 2 weeks with no activity.