- Issue created by @alexpott
- First commit to issue fork.
- Merge request !52Issue #3454099 - Update file ContentLockSettingsForm.php → (Closed) created by immaculatexavier
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
@immaculatexavier that's not how #config_target works - it allows you to map form elements to config values - see https://www.drupal.org/node/3373502 →
It'll be quite complicated for this form because of how the config is mapped to and from the form.
- 🇮🇳India immaculatexavier
Hi @alexpott,
Created MR Accidentally without seeing your previous message.
- First commit to issue fork.
- 🇺🇦Ukraine AstonVictor
I don't think it is worth to update the form to use #config_target.
I guess it's not possible to use it with the current implementation of form elements because we collect all information in the submit callback and save them to the correct properties.
The config target only allows to convert the field value from the config value to the default value and from the submitted value to the config value. That's not our case.
Updating the form leads to updating the config structure and refactoring using configs in all other places. And it requires implementing an update hook to use a new mapping of config properties.
Currently, there are no advantages to using it.