Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
remove internal meta-data #3020
fixing it in
See also #2700 (currently open because the global position for spec does not work).
A plugin running after
Note: I actually have no idea, where the
Fixing it in
IMO there has to be a way to mark metakeys (and maybe even normal keys) for automatic removal. All the marked keys should then be automatically removed, before the storage plugin is called.
We once discussed that spec should be the vacuum cleaner to fix everything that is wrong with metadata.
The idea was that spec will be the very last plugin.
Yes, if the metadata is added during
There is no need for automatic removal because the semantics as given in doc/METADATA.ini already tell us what should be removed and what is needed for storage plugins. The spec plugin would need a list of metadata to be removed. This is not super-pretty but the alternatives need code-generation which is too much for 1.0 now.
Yes, I know (#2700 (comment)), but it is not possible right now. I also think
If we don't want to do the cleanup in the core (or the new backend plugin), it should be a separate cleanup plugin.
I don't know, where the
It might be true that
Fair point. We can also make a new
Nothing should vanish between
For the removal code: certainly. Overall: I do not know. There are many plugins that set metadata to be removed, they all would need to be changed to mark their metadata.
Furthermore, this would open the door for many different markers. E.g. for storage plugins we might want to remove different meta-data as for exporting configuration.