Currently, the require_on_publish third-party setting is added in the require_on_publish_field_config_submit() form submit handler. However, this handler is only called when fields are created or edited via the UI.
When a FieldConfig entity is created programmatically (e.g., in test setup or install profiles), this submit handler is bypassed, and the setting is never added—resulting in inconsistent behavior.
$field = FieldConfig::create([
'entity_type' => 'node',
'bundle' => 'article',
'field_name' => 'field_tags',
'label' => 'Tags',
'required' => FALSE,
]);
$field->setThirdPartySetting('require_on_publish', 'require_on_publish', TRUE);
$field->save();
Refactor the logic in require_on_publish_field_config_submit() so that:
This ensures that if the require_on_publish form value is passed via $field->setThirdPartySetting() during programmatic creation, it is consistently processed and validated.
Never mind. This only becomes a problem when we introduce #states Form API handling. Providing the third-party setting programmatically is the correct path forward for tests in ✨ Add support for multi-value fields like Name and Address fields Active . Postponed until we work on ✨ Add require on publish as a conditional field option Active .