Description of the need
This is a developer experience improvement proposal: When disabling a field in a display mode, every field on the content type gets updated due to the field weights being re-numbered. Similarly, if you arrange the enabled fields, all fields (including disabled ones) get their weights updated. This results in unnecessary configuration file changes, which can more easily lead to merge conflicts for people managing configuration in version control.
Proposed solution
The weights for disabled fields should not be stored at all (IMO), they should default to the main field weight specified by the field configuration. Disabling a field should not modify any other fields' weight. (Though enabling a field almost certainly will modify weight, since it needs to be positioned).
Recent comments
I am considering migrating my drupal 7 website to backdrop. Hi @seamus, I would like to offer my professional services for migration to BackdropCMS. Please connect If...
drupal 7 to backdrop migration
Restore Newsletter Subscriptions from a Database Backup One of my websites was affected by the Simplenews issue, and there were many incorrectly disabled newsletter subscriptions of '...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
This is the report about the recently discovered bug: https://github.com/backdrop-contrib/simplenews/issues/83. First, how do you know if your site is affected? In other words: Are there...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled