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
This has always been available using a separate module. Now added to the core, thanks for developers.
Gallery inside post content
It's the reason why i refuse "builder" because finally, you have a "student blog". But a gallery it's not a crazy thinks. All CMS propose it. Too many constraints can also scare your...
Gallery inside post content
There is such a thing as a "publication format" — all publications must be made in the same style, which was developed by the designer, and the task of the editor is to fill in the provided...
Gallery inside post content