There are no constraints for the parent base field in core, but if a contrib/custom module adds a constraint to the base field, the violations will be removed in validation of the content entity form.
Parent base field does not have a component in the form display, but is added directly in the form, so the field will be missing from:ContentEntityForm::getEditedFieldNames
So those fields violations will be removed: ContentEntityForm::216
$violations->filterByFields(array_diff(array_keys($entity->getFieldDefinitions()), $edited_fields));
This means that the violations are removed, and the entity is saved although it shouldn't.
1. Override getEditedFieldNames and add the field
2. Override flagViolations to flag the correct form element
as described in the docblocks in ContentEntityForm.
Solve the bug.
No.
MenuLinkContentForm will override 2 methods. However, MenuLinkContentForm is marked internal, so we should be fine.
Needs work
11.0 🔥
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I can confirm patch in #3 is still solving the issue in Drupal 9.4
Triaging as part of Bug Smash Initiative. Looks like this needs a re-roll as well as still needing a test.
Re-rolled patch against 11.x. Keeping it Needs work for test as mentioned in #12