- Issue created by @catch
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
Is this a duplicate of #2997100: Introduce a way to deprecate config schemas → ?
- 🇬🇧United Kingdom catch
Re-purposing this to use the existing API for this views key.
Not sure how viable this is but opening for discussion.
The removal of default_argument_skip_url affects 180+ contrib modules but because the deprecation layer is entirely runtime (trigger_error()) it's not possible to detect outside runtime.
🐛
Add proper deprecation notices in config entity presave bc layers
Active
is dealing with the fact we haven't always done the trigger_error() properly but I wonder if we can do something beyond that.
The idea would be to add something to the config schema layer that indicates that a key is deprecated - this would potentially allow upgrade_status to know which config schema keys are deprecated then warn when it finds that key in a module.
It could also help us to trigger the deprecation message generically in core when config is saved with that key, which would help a subset of config update issues (obviously wouldn't help with more restrictive values etc., just removing keys). e.g. we might be able to keep that in longer than the update paths themselves?
We've added deprecation support to other YAML before - libraries support both deprecated and the new 'moved_files' syntax.
Active
11.0 🔥
Last updated
Is this a duplicate of #2997100: Introduce a way to deprecate config schemas → ?
Re-purposing this to use the existing API for this views key.