Use #config_target in the settings form for an indication of overridden configuration

It's not well documented in Drupal (it took me a while to find anything about this) and I saw that `#config` was changed to `#config_data_store` in the newer Drupal versions.

In this issue of Drupal core they are talking about the fact that Drupal should indicate if a config value was overridden. So, for newer Drupal in the future, it would be recommended to add `#config_data_store`. Please see https://www.drupal.org/project/drupal/issues/2408549 🐛 Display status message on configuration forms when there are overridden values Fixed

Seems like it will be postponed on 🐛 Display status message on configuration forms when there are overridden values Fixed

🐛 Display status message on configuration forms when there are overridden values Fixed was committed in Drupal Core, so this issue is no longer postponed.

Updated the issue summary.

MR appears to have issues

The pipeline is currently broken, but the MR is fine. I filed a separate issue at 📌 Widen dependency options for next major testing Active

#config_target is supported from Drupal Core 10.2 and later, see https://www.drupal.org/node/3373502 →

Will have think of something here. Can't just add a version restriction out of the blue on people

Didn't mean to change status

Check https://www.drupal.org/project/scheduled_transitions → for a project that runs different branches with different version requirements.

The 3.0.x is not yet documented on the project page, so I'm not sure what the occasion was to open a new major branch?

So 🐛 Display status message on configuration forms when there are overridden values Fixed only made it into 10.4 if was going to make a new branch feel may need to target that.

smustgrave → closed merge request !76

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