You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 18, 2019. It is now read-only.
On an internal project using kegan, @derwolfe noted that maybe kegan could do a better job ordering some of its results. Right now kegan internally produces sets of paths and values. This means that there's no meaningful ordering to them.
I think this means ordering paths such that shorter paths come first; equal length paths are lexographically sorted. It might make sense to make this optional.
While it currently produces sets, maybe it should produce seqs and not promise anything about order; leaving the set part to the tests only.
On an internal project using kegan, @derwolfe noted that maybe kegan could do a better job ordering some of its results. Right now kegan internally produces sets of paths and values. This means that there's no meaningful ordering to them.
It would be nice if these were ordered in a slightly better order for human inspectability:
I think this means ordering paths such that shorter paths come first; equal length paths are lexographically sorted. It might make sense to make this optional.
While it currently produces sets, maybe it should produce seqs and not promise anything about order; leaving the set part to the tests only.