{"action":"reopened","issue":{"url":"https://api.github.com/repos/mostaphaRoudsari/honeybee/issues/655","repository_url":"https://api.github.com/repos/mostaphaRoudsari/honeybee","labels_url":"https://api.github.com/repos/mostaphaRoudsari/honeybee/issues/655/labels{/name}","comments_url":"https://api.github.com/repos/mostaphaRoudsari/honeybee/issues/655/comments","events_url":"https://api.github.com/repos/mostaphaRoudsari/honeybee/issues/655/events","html_url":"https://github.com/mostaphaRoudsari/honeybee/issues/655","id":255089445,"number":655,"title":"Search across Ladybug & Honeybee","user":{"login":"devngc","id":20086924,"avatar_url":"https://avatars0.githubusercontent.com/u/20086924?v=4","gravatar_id":"","url":"https://api.github.com/users/devngc","html_url":"https://github.com/devngc","followers_url":"https://api.github.com/users/devngc/followers","following_url":"https://api.github.com/users/devngc/following{/other_user}","gists_url":"https://api.github.com/users/devngc/gists{/gist_id}","starred_url":"https://api.github.com/users/devngc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/devngc/subscriptions","organizations_url":"https://api.github.com/users/devngc/orgs","repos_url":"https://api.github.com/users/devngc/repos","events_url":"https://api.github.com/users/devngc/events{/privacy}","received_events_url":"https://api.github.com/users/devngc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":18,"created_at":"2017-09-04T17:00:16Z","updated_at":"2018-03-15T17:01:12Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Hello Everyone,\r\n\r\n[Some Background]\r\nUsually, you when you're looking up code inside a component, You want to look up a function from Ladybug_Ladybug or Honeybee_Honeybee, and so you find that function in Ladybug_Ladybug or Honeybee_Honeybee. It's straightforward.\r\n\r\nRecently, while working on a component, I found myself in a reverse situation. I knew a function in Honeybee_Honeybee and I had to find all the components using it. Therefore, I wrote a few lines to look through all the .Py files in C:\\ladybug\\honeybeeSrc\\honeybee-master\\src to get the only files using the function I was looking for.\r\n[End of Background]\r\n\r\nWhile doing this, it occurred to me that we can do something similar to perform a keyword search through all Ladybug and Honeybee .Py files.\r\n![rainman](https://user-images.githubusercontent.com/20086924/30034374-877da08a-91be-11e7-988b-b82cadb4a54a.jpg)\r\n\r\nIn the image above, you can see what happens when you search for \"Drybulb.\" The native GH search is not very helpful. \r\n\r\nI am proposing we have a component that \r\n1. Looks through the args, returns, and description of all the components\r\n2. Ranks them based on hits \r\n3. Returns a list of the names of the components.\r\n\r\nWhat you see in the image is really primitive. I believe I can refine the results to be more specific. The idea is to receive a list of components that deal with (Either takes it as input or outputs it) the query (keyword).\r\n\r\nI am raising this issue to trigger a discussion. **I would be very glad to hear your thoughts on whether this should be a part of Ladybug Suite.** \r\n\r\n\r\n\r\nThank you!\r\nDevang\r\n"}}
{"actor":{"display_login":"devngc"}}