racksec / kegan Goto Github PK

Some observations:

1. I'm the primary author either during my time at Rackspace or currently at Latacora
2. Latacora is using it, and AFAICT Rackspace isn't
3. I'm the only person who can push releases anyway
4. We'll be pretty happy to keep maintaining it

It seems like the most straightforward way to fix these issues is to transfer ownership of the repo to me :-)

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.

[["1" :b :c] 3 4]
[["1" :a] 1 2]
[["1" :b :d] 5 6]

It would be nice if these were ordered in a slightly better order for human inspectability:

[["1" :a] 1 2]
[["1" :b :c] 3 4]
[["1" :b :d] 5 6]

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.