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
In #3223 I proposed a change to directoryvalue, that would avoid the possible collisions that the base name
Storage plugins have to have some mechanism to store metadata. So why not move the problematic key's value into metadata?
This might seem like we are just moving the problem, but we are not. There is already precedence for metakeys having special semantics. For example, the way
Now, we could either abuse the
I also still think, that
I do not see how metadata can help here. The purpose of directoryvalue is circumvent limitations of configuration file formats, so it needs to encode data within key names and key values, as no other place is available to store the additional information.
The only "problem" directoryvalue has is that it would not work if someone actually would like to store
This makes writing of storage plugins even harder as it already is. The advantage of directoryvalue as plugin is that it works completely transparent. The storage plugin gets the guarantee that the directories will not have values and do not need to do anything to handle these situations.