Last modified: 2014-06-24 15:01:28 UTC
One problem with implementing this is that following the naive approach (representing a change in order as a remove and an insert operation), both such operations would have the same key in the (Map)Diff, so one would override the other. Also, for the insert operation, it would need some context specifying *where* to insert it. An alternative approach is to represent the order explicitly as a list of keys, and attach that list as an extra field to the MapDiff. Note that the class tree based in the Diff class contains some overburdened and some deprecated classes. Some refactoring may be in order. Also, care must be taken to allow for reliably application of Diffs as patches.
Wikidata crew: This has been highest priority since 2013-12-10. Any news here?
Now at https://github.com/wmde/Diff/issues/4
Reopen this to not forget it when not following the issues on GitHub.
(In reply to tobias.gritschacher from comment #4) > Reopen this to not forget it when not following the issues on GitHub. Is this ticket still "highest priority" which was set half a year ago?
(In reply to tobias.gritschacher from comment #4) > Reopen this to not forget it when not following the issues on GitHub. Is this ticket still "highest priority" which was set half a year ago? If yes, we might have different interpretations of highest priority. ;)
