Add a "tree" view

[coxley]

Hound is super simple to deploy, but hundreds of repos to search through it gets quite hard to parse. I suggest having a view to "minimize" the repo names where matches were found and let the user expand them?

[dcampbell24]

If I understand you, that sounds like a super helpful feature to have. The results would start off as just the book icons with the repo name next to it (maybe add some stats like how many matches were in the repo) and then clicking on the book icon would cause results to be expanded. The icon could be clicked on further times to toggle back and forth and would probably display a different looking book (open or closed).

I think for when files have a lot of matches it might be nice if the lines within the file where the matches were started hidden and then could be toggled. There might also be some expand and collapse all buttons.

[coxley]

That about sums up my thoughts. :)

[danielcb]

#149

[mikepurvis]

I'm interested in this feature too; we also have 100+ repositories at our org.

Has anyone done an implementation?

[grahamhayes]

I have found http <server>/api/v1/search q=<query> repos='*' -f | jq '.Results | keys' using httpie and jq (should work fine with curl as well) gets the name of the repos.

e.g.

➜  designate git:(master) http http://codesearch.openstack.org/api/v1/search q=ujson repos='*' files="requirements\.txt" -f | jq '.Results | keys' 
[
  "kiloeyes",
  "monasca-common",
  "requirements",
  "rpm-packaging"
]