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
Thanks, but that makes no difference. I enter Today as the end, Apply, it ignores it, and I still have just the one date selector.
Between Dates Views Filter not functioning as expected
But when setting End Date, and relative of -0 days or -1 days... Instead of "-0 days" use today and instead of -1 days use yesterday. Find some background re relative...
Between Dates Views Filter not functioning as expected
Worth mentioning as it was in zulip chat by @yorkshirepudding I just tested and the two work together without issue as long as you don't use the "Exclude comments from Content...
Search does not include comments