Forcing nodes to maintain original sort?

[veltman]

As far as I can tell nodes() will return its results in sorted position order, rather than the order the nodes were originally supplied in. This seems a little unexpected, and makes it hard to collate between the nodes and other lists (e.g. two separate label computations on both sides of a slope chart) or do things like draw in some original priority order. Am I interpreting the results right? Would it make sense to include sort: false as a possible option, so the order can be stable?

[kristw]

Thanks for reporting. This was not intentional. There was a line of code that does the in place sorting without copying the array first. I have made the fix and published as v1.1.3.