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
Hi geoma, no need to excuse. I think, now I got it (more or less). Your problem doesn't actually have much to do with the Leaflet module, but you struggle with the combination of...
Parent items won't show on Leaflet Widget.
Sorry for not being clear. I have this view and two exposed filters on it. I am trying to show different places on the map. These places are called "institutions". They have a...
Parent items won't show on Leaflet Widget.
Still trying to understand: you have this view and an exposed form on it, right. And you have two independent taxonomy terms and try to filter by them? Or is this a hierarchal...
Parent items won't show on Leaflet Widget.