- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
✨ Provide an easier way for developers to identify entity/field definition mismatches Active was created earlier and neither have a patch, so closing this as a duplicate
The list of errors/issues under the "Entity/field definitions" mismatch section of the status report is confusing at best (esp. for novice/non-technical site owners) and frustratingly vague at worst (esp. for power users/developers.)
These issues can stem from all sorts of issues ranging from the relatively benign (missing update hooks for non-critical things) to the significant (mismatched property schema, e.g. as was the case in #3230076: PurchasableEntityInterface should extend EntityInterface, not ContentEntityInterface → ). However they're all surfaced with the same severity and with little to go on.
The checks underneath the hood on these errors check a ton of different entity and field characteristics inside of huge if() blocks, meaning there's no granular information collected at the time of evaluation as to which of these checks failed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
✨ Provide an easier way for developers to identify entity/field definition mismatches Active was created earlier and neither have a patch, so closing this as a duplicate