Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
cascading import/export/editor dangerous #2762
cascading import/export/editor are currently not implemented and should fail until we have implemented it. As solution write to import/export/editor all namespaces separately (even though then validation does not work
One recent problem: In #2760 the last import removed the spec key.
That is probably a merging problem. It seems
In a more complicated example with a full LCDproc config, I actually got merging conflicts and import failed.
The only way I see any of these working, is like this:
That shouldn't be too hard to implement. It already works like this in
Anything actually involving some sort of cascading lookup where different namespaces are mixed together would only cause problems. It would also be very intransparent.
Thank you for the input!
Of course it would be better if it works. Otherwise @Piankero can also simply let it fail when cascading keys are given.