ECA Content - field value changed condition with base field overrides
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3502635. -->
Reported by: [rapking](https://www.drupal.org/user/3839897)
Related to !465
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>The field value changed condition always returns true (or false if negated) when using a base field override on a boolean field.</p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<p>1. Ensure you have a base field override on a boolean field.<br>
For example: Uncheck the default option for the “Promoted to front page" base field on a content type configuration form.<br>
2. Use the overridden field in an “Entity: field value changed" condition of your workflow.<br>
3. Observe that your condition stays the same whether the field value was changed or not.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>There is already logic in place to fix strict checking on boolean and entity reference field types. If we apply that logic to FieldConfigInterface rather than FieldConfig, it will cover this extended case. Both FieldConfig and BaseFieldOverride implement FieldConfigInterface.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<h3 id="summary-ui-changes">User interface changes</h3>
<h3 id="summary-api-changes">API changes</h3>
<h3 id="summary-data-model-changes">Data model changes</h3>
issue