{"action":"opened","issue":{"url":"https://api.github.com/repos/aperezdc/ngx-fancyindex/issues/56","repository_url":"https://api.github.com/repos/aperezdc/ngx-fancyindex","labels_url":"https://api.github.com/repos/aperezdc/ngx-fancyindex/issues/56/labels{/name}","comments_url":"https://api.github.com/repos/aperezdc/ngx-fancyindex/issues/56/comments","events_url":"https://api.github.com/repos/aperezdc/ngx-fancyindex/issues/56/events","html_url":"https://github.com/aperezdc/ngx-fancyindex/issues/56","id":183807441,"number":56,"title":"Provide tooling which allows parsing HTML in unit tests easily","user":{"login":"aperezdc","id":723451,"avatar_url":"https://avatars.githubusercontent.com/u/723451?v=3","gravatar_id":"","url":"https://api.github.com/users/aperezdc","html_url":"https://github.com/aperezdc","followers_url":"https://api.github.com/users/aperezdc/followers","following_url":"https://api.github.com/users/aperezdc/following{/other_user}","gists_url":"https://api.github.com/users/aperezdc/gists{/gist_id}","starred_url":"https://api.github.com/users/aperezdc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aperezdc/subscriptions","organizations_url":"https://api.github.com/users/aperezdc/orgs","repos_url":"https://api.github.com/users/aperezdc/repos","events_url":"https://api.github.com/users/aperezdc/events{/privacy}","received_events_url":"https://api.github.com/users/aperezdc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/aperezdc/ngx-fancyindex/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/aperezdc/ngx-fancyindex/labels/good%20first%20bug","name":"good first bug","color":"0e8a16"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-18T21:26:08Z","updated_at":"2016-10-18T21:26:08Z","closed_at":null,"body":"Being able to parse the HTML returned by the module from shell scripts would allow greatly improving the test suite. For example, some tools like the following could be up to the task:\r\n\r\n* [pup](https://github.com/EricChiang/pup) (written in Go, likely not readily available from distribution packages in Travis-CI, but works reall well.)\r\n* [This answer at Stack Exchange](http://unix.stackexchange.com/questions/6389/how-to-parse-hundred-html-source-code-files-in-shell) points also to `hxselect`, included in W3C's [html-xml-utils](https://www.w3.org/Tools/HTML-XML-utils/README) package. (This may be easier to get in Travis-CI.) \r\n* ...\r\n\r\nThis task means searching for a readily available alternative, if possible. Otherwise, probably providing a static build of `pup` that the unit tests can use would work — probably there's no need to build it in the CI."}}
{"actor":{"display_login":"aperezdc"}}