Add schema definitions for third party for Field Widget Actions

I'm not sure about the proposed fix… feels too simple. But in case it's on the right track…

So I tested it after deleting all automators from admin/structure/types/manage/article/automator_chain and uninstalling & re-installing the module.

• Then I enabled Automators on the Article field_tags to generate 3 tags;
• Configured the FWA button in admin/structure/types/manage/article/form-display;
• Saved and the schema warnings are gone;
• Then tested the FWA button in the edit form, and it works as expected;

Let me know

Adding some of the error messages in case it helps. There is a pattern…

Schema errors for core.entity_form_display.node.page.default with the following errors: core.entity_form_display.node.page.default:content.field_extracted_emails.third_party_settings.field_widget_actions.new missing schema, core.entity_form_display.node.page.default:content.field_extracted_emails.third_party_settings.field_widget_actions.db87611c-0931-4259-8a63-6109b6f48320 missing schema.

Schema errors for core.entity_form_display.node.article.default with the following errors: core.entity_form_display.node.article.default:content.field_tags.third_party_settings.field_widget_actions.new missing schema, core.entity_form_display.node.article.default:content.status.third_party_settings.field_widget_actions.new missing schema.

Schema errors for core.entity_form_display.node.page.default with the following errors: core.entity_form_display.node.page.default:content.field_sentiment_score.third_party_settings.field_widget_actions.new missing schema, core.entity_form_display.node.page.default:content.field_sentiment_score.third_party_settings.field_widget_actions.20fe9acd-8936-4e9d-89f8-3e718e64865f missing schema.

Well, FWA can not know what third-party settings will be made by third parties. So, there are 2 possible ways:

Either we indeed let the validator ignore the third-party settings, that's what's proposed in the MR.

Or, if we don't want that to happen, we need to enforce a schema definition for this section by each implementing module, and if they don't do that, the user will see the warnings, or wouldn't be able to import config entities, depending on setup.

So, I don't know if the latter is realistic, although that option would certainly be prepeferred.