Problem/Motivation

At the moment if your custom config entity doesn't implement config_export annotation or config schema you can get an exception when toArray is called. The exception message tells you config schema is missing. But the config schema for determining which properties to export is deprecated so we should fix the message.

Found as part of #3112639: Remove all @deprecated code from config component

Proposed resolution

Improve the message. #3113620: Require `config_export` annotation for config entity types and improve ConfigEntityType::getPropertiesToExport() will handle either improving the class name or removing it entirely.

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

Release notes snippet

N/a

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alexpott created an issue. See original summary.

alexpott’s picture

Status: Active » Needs review
FileSize
1.74 KB
Berdir’s picture

Status: Needs review » Reviewed & tested by the community

Makes sense.

Gábor Hojtsy’s picture

  • Gábor Hojtsy committed 3003e5d on 9.0.x
    Issue #3113633 by alexpott, Berdir, catch: Improve schema incomplete...

  • Gábor Hojtsy committed 77e657d on 8.9.x
    Issue #3113633 by alexpott, Berdir, catch: Improve schema incomplete...
Gábor Hojtsy’s picture

Status: Reviewed & tested by the community » Fixed

Looks good. Credited @catch as he suggested this breakout issue. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.