{"action":"closed","issue":{"url":"https://api.github.com/repos/jamalneufeld/ghostHunter/issues/58","repository_url":"https://api.github.com/repos/jamalneufeld/ghostHunter","labels_url":"https://api.github.com/repos/jamalneufeld/ghostHunter/issues/58/labels{/name}","comments_url":"https://api.github.com/repos/jamalneufeld/ghostHunter/issues/58/comments","events_url":"https://api.github.com/repos/jamalneufeld/ghostHunter/issues/58/events","html_url":"https://github.com/jamalneufeld/ghostHunter/issues/58","id":324742196,"number":58,"title":"Multiple distinct indexes in different areas of a site?","user":{"login":"TaoK","id":531704,"avatar_url":"https://avatars2.githubusercontent.com/u/531704?v=4","gravatar_id":"","url":"https://api.github.com/users/TaoK","html_url":"https://github.com/TaoK","followers_url":"https://api.github.com/users/TaoK/followers","following_url":"https://api.github.com/users/TaoK/following{/other_user}","gists_url":"https://api.github.com/users/TaoK/gists{/gist_id}","starred_url":"https://api.github.com/users/TaoK/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TaoK/subscriptions","organizations_url":"https://api.github.com/users/TaoK/orgs","repos_url":"https://api.github.com/users/TaoK/repos","events_url":"https://api.github.com/users/TaoK/events{/privacy}","received_events_url":"https://api.github.com/users/TaoK/received_events","type":"User","site_admin":false},"labels":[{"id":77033725,"url":"https://api.github.com/repos/jamalneufeld/ghostHunter/labels/question","name":"question","color":"cc317c","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-05-20T20:59:06Z","updated_at":"2018-05-24T09:28:26Z","closed_at":"2018-05-24T09:28:26Z","author_association":"NONE","body":"Hi, I'm using ghost in a maybe-unusual way, with multiple substantially-distinct sets of stories in a single ghost instance.\r\n\r\nDifferent sets of stories coexist and display in different areas of the site, with tags controlling what shows where.\r\n\r\nIn my case I happen to be implementing a multi-language site (under a single ghost instance), but I could imagine other use-cases for this type of tag-based partitioning.\r\n\r\nSo, what I'm wondering is what it would take to support \"filtered indexing\" in ghosthunter, whereby I would pass in, at initialization time, the tag filters that I want passed into the ghost API.\r\n\r\nIn my case I would only ever want one search on any one page of the site, so I don't need to worry about encapsulating configuration/initialization properties that are currently \"global\" in the ghosthunter plugin object.\r\n\r\nAs far as I could tell this should be very straightforward, with only two important changes to be made:\r\n\r\n1. Add support for passing the filter in, and having it be passed through to the ghost API call in indexing\r\n\r\n2. Ensure that the localstorage key (at index setting and retrieval time) is updated to include the filter key (or some other explicitly passed in identifier).\r\n\r\nIs there anything else I'm clearly missing in this proposed scheme?"}}
{"actor":{"display_login":"Windyo"}}