Allow configuration schema fallback in ConfigEntityType::getPropertiesToExport() to work without an ID

Created on 5 May 2015, over 9 years ago
Updated 20 February 2024, 10 months ago

Follow-up to #2432791: Skip Config::save schema validation of config data for trusted data β†’

Problem/Motivation

#2432791-83: Skip Config::save schema validation of config data for trusted data β†’ has an improvement and has been missed as part of #2432791: Skip Config::save schema validation of config data for trusted data β†’

Proposed resolution

Fix it.

Remaining tasks

  • Review
  • Commit

User interface changes

None

API changes

None

Beta phase evaluation

<!--Uncomment the relevant rows for the issue. -->

-->

πŸ“Œ Task
Status

Needs work

Version

11.0 πŸ”₯

Component
Configuration entityΒ  β†’

Last updated 3 days ago

Created by

πŸ‡¬πŸ‡§United Kingdom vijaycs85 London, UK

Live updates comments and jobs are added and updated live.
  • Performance

    It affects performance. It is often combined with the Needs profiling tag.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

  • Contributed project blocker

    It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024