I created an issue fork and pushed the changes up to #37 which apply to 10.1.x
I didn't include the tests provided #54 since the patch in that comment was based on the older implementations (as per #60) and because I was not sure if they would be relevant (as per #44)If you think that they should be included, feel free to commit and update the issue.
The interdiff I provide is just the missing one between 29 and 37.
- last update
about 1 year ago 30,326 pass, 2 fail - 🇧🇪Belgium borisson_ Mechelen, 🇧🇪
📌 Deprecate the trusted data concept in configuration Active will remove the trusted data concept entirely, and I think what this issue is doing, ignoring config schema errors, is the complete opposite of all of the config schema validation work we've been doing lately.
This is because contrib/custom code doesn't always provide a correct schema, and instead of hiding the errors, I think we should guide maintainers to write correct and complete schema's.
- 🇺🇸United States SocialNicheGuru
For #65 watchdog_exception is deprecated. https://www.drupal.org/node/2932520 →
- 🇺🇦Ukraine pifagor 🇺🇦 Rivne
@natnatalia Part for Config.php is present in version 10.3.0, so the patch cannot be applied. Maybe only the tests need updating
- 🇺🇸United States gcalex5
Re-roll #73 to remove the
/site/prefix that was preventing it from applying. - 🇵🇱Poland sokolff Wroclaw
I can confirm that patch #75 works fine for Drupal 10.3.0. Thank you!
- 🇺🇦Ukraine olmyr Ukraine, Kharkiv
Hello,
#75 🐛 Invalid config structures can result in exceptions when saving a config entity Needs work works with 11.0.4 - 🇨🇦Canada francismak
Patch #75 works for 10.3.6, thank you! Putting more details here.
For our case, we are using a 'or' operator in views when filtering a taxonomy term.
Our config import was working in 10.2, but got error in 10.3.6The configuration property display.block_1.display_options.filters.field_data_target_id.value.983 doesn't exist.In the config yml, I removed the values with issues, and replaced with {} instead, and able to import. Then navigate to that view, tried to add back the 'or' filtering to that term and save:
InvalidArgumentException: The configuration property display.block_1.display_options.filters.field_data_target_id.value.983 doesn't exist. in Drupal\Core\Config\Schema\ArrayElement->get() (line 95 of core/lib/Drupal/Core/Config/Schema/ArrayElement.php).Once patch #75 applied, both import and view saving are now working properly.
