{"action":"opened","issue":{"url":"https://api.github.com/repos/thebritican/elm-autocomplete/issues/37","repository_url":"https://api.github.com/repos/thebritican/elm-autocomplete","labels_url":"https://api.github.com/repos/thebritican/elm-autocomplete/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/thebritican/elm-autocomplete/issues/37/comments","events_url":"https://api.github.com/repos/thebritican/elm-autocomplete/issues/37/events","html_url":"https://github.com/thebritican/elm-autocomplete/issues/37","id":179653592,"number":37,"title":"subscription for keyboard up/down arrow","user":{"login":"ericgj","id":291002,"avatar_url":"https://avatars.githubusercontent.com/u/291002?v=3","gravatar_id":"","url":"https://api.github.com/users/ericgj","html_url":"https://github.com/ericgj","followers_url":"https://api.github.com/users/ericgj/followers","following_url":"https://api.github.com/users/ericgj/following{/other_user}","gists_url":"https://api.github.com/users/ericgj/gists{/gist_id}","starred_url":"https://api.github.com/users/ericgj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ericgj/subscriptions","organizations_url":"https://api.github.com/users/ericgj/orgs","repos_url":"https://api.github.com/users/ericgj/repos","events_url":"https://api.github.com/users/ericgj/events{/privacy}","received_events_url":"https://api.github.com/users/ericgj/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-28T00:46:27Z","updated_at":"2016-09-28T00:46:27Z","closed_at":null,"body":"Just wanted to confirm, in order to get menu navigation behavior with the keyboard, you have to `Sub.map` the autocomplete subscription, all the way up your app tree, correct?  Essentially menu navigation is done through a global keyboard handler -- which is why in the examples you do NoOp + `stopPropagation = false` for up/down arrow keydowns in the input element?\r\n\r\nIf so, I'm having a bit of a dilemma. On the one hand, I would prefer to have my list of items _not_ be part of the model state, but be passed in separately as config/context/props, for reasons mentioned in #36 . But this bit of context (a little detail like the list of items!) wouldn't be available when the Keyboard subscription bubbles up, so there's no way to update the menu based on these keyboard events.\r\n\r\nMaybe there is no other way but including the list in the model, but that is extremely inconvenient from the point of view of how typical state trees are constructed :(  at least in my understanding.\r\n"}}
{"actor":{"display_login":"ericgj"}}