Confirm Semi-coupled form elements can work with State API visibility

Thi

bnjmnm → changed the visibility of the branch 3481719-confirm-semi-coupled-form to hidden.

The Radix version on 0.x

The native version in this MR

Is this at a state where it can be tried with Pathauto and other entity form extending modules? :) Or can you signal when it is? :)

@gábor hojtsy the scope of this issue includes getting the pathauto widget functional. With this MR. The form elements in that widget work as expected and send the correct data for submission. The autosave data is aware of pathauto being enabled/disabled and the value of the custom alias.

However, the publish process is not processing these values correctly. This.is out of scope for this widget-targeted issue. Even if it's out of scope, I figured it can't hurt to offer an additional draft MR 3481719-states-api-with-targeted-pathauto that takes the in-scope MR and adds a few lines to ApiAutoSaveController to get pathauto working

 if (get_class($entity->path) === 'Drupal\pathauto\PathautoFieldItemList' && $auto_save['data']['entity_form_fields']['path[0][pathauto]'] === FALSE) {
          $entity->path->__set('pathauto', 0);
        }

I believe this is necessary because the publish process updates fields, but path is being updated as an entity property.
I suspect there are more holistic solutions available so the 3481719-states-api-with-targeted-pathauto branch should probably not be part of this issue's commit, so I created 🐛 Autosave publish process does not acknowledge pathauto deactivation Postponed , which can use the solution I already found as a starting point.

left some comments

Looks good to me! but still needs a /ui/src/components/form/inputBehaviors.tsx approval

bnjmnm → credited balintbrews → .

Thanks for the reviews @hooroomoo & @balintbrews