Upstream maintainer here. That will probably never happen, because that’s not wanted. Applications should not depend on dconf directly, but should instead use a GLib.Schema that defines which keys could be used, and so makes manually adding keys meaningless.
There has been a concern in all stable releases until now because of relocatable schemas, that were not mapped to their paths; that is solved (imperfectly, but people shouldn’t notice) in the future 3.28, that will be release in March 2018. The same problem will happen again with the growing use of Flatpak (or similar technologies), but the solution should be and will probably be (as I’m the maintainer…) to wait until a real fix is found, instead of allowing to add dconf keys manually. Hope you’ll understand this point of view. :) -- Arnaud Bonatti ________________________________ courriel : arnaud.bona...@gmail.com