Views configuration should not store unused data

Created on 21 March 2014, about 11 years ago
Updated 18 December 2024, 4 months ago

I just removed a field(currency) from views and also a value override of another field(price, which appended the currency to the price value). Then I've exported the View configuration file and I've noticed that:
a) the value overriding string was still present(though the overriding was disabled)
b) the removed field was present in fields list with 0 as value(I presume it means it's disabled/hidden..).

Anyway I'm sure there are tons of these unused values.

I'm OK with them being present in the site's config but when I export it I expect these thing to be "cleaned out" so if I reinstall the module I won't be importing this unused stuff.

I think this should be done by comparing the config schema with the config file and removing the data with the same values that are in the schema.

When I think about it I'm not sure if it's Views' issue or Configuration management's issue.

📌 Task
Status

Closed: duplicate

Version

11.0 🔥

Component

views.module

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024