{"action":"created","issue":{"url":"https://api.github.com/repos/mjackson/history/issues/240","repository_url":"https://api.github.com/repos/mjackson/history","labels_url":"https://api.github.com/repos/mjackson/history/issues/240/labels{/name}","comments_url":"https://api.github.com/repos/mjackson/history/issues/240/comments","events_url":"https://api.github.com/repos/mjackson/history/issues/240/events","html_url":"https://github.com/mjackson/history/issues/240","id":139492806,"number":240,"title":"[meta] Ship v3","user":{"login":"mjackson","id":92839,"avatar_url":"https://avatars.githubusercontent.com/u/92839?v=3","gravatar_id":"","url":"https://api.github.com/users/mjackson","html_url":"https://github.com/mjackson","followers_url":"https://api.github.com/users/mjackson/followers","following_url":"https://api.github.com/users/mjackson/following{/other_user}","gists_url":"https://api.github.com/users/mjackson/gists{/gist_id}","starred_url":"https://api.github.com/users/mjackson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mjackson/subscriptions","organizations_url":"https://api.github.com/users/mjackson/orgs","repos_url":"https://api.github.com/users/mjackson/repos","events_url":"https://api.github.com/users/mjackson/events{/privacy}","received_events_url":"https://api.github.com/users/mjackson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2016-03-09T06:56:25Z","updated_at":"2016-03-14T16:33:42Z","closed_at":null,"body":"After f12d632691ebef652d0cf5dd67a033e87746fc4a I'm ready to ship v3. Looking through the list of open issues, a lot of stuff seems like extreme edge cases that we can fix in patch releases. At this point I'm looking for any major API changes that need to happen before the next major release.\r\n\r\nStuff that's on my mind:\r\n\r\n- #135 Make relative paths work. We already have the concept of a \"current location\" in the `createHistory` closure. Seems like we'll just need to resolve relative paths against that in order to make it work.\r\n- #231 Drop the default location in memory history. @timdorr thinks this needs to go, but I'm not 100% sure why.\r\n\r\nAnything else?"},"comment":{"url":"https://api.github.com/repos/mjackson/history/issues/comments/196400601","html_url":"https://github.com/mjackson/history/issues/240#issuecomment-196400601","issue_url":"https://api.github.com/repos/mjackson/history/issues/240","id":196400601,"user":{"login":"taion","id":3112159,"avatar_url":"https://avatars.githubusercontent.com/u/3112159?v=3","gravatar_id":"","url":"https://api.github.com/users/taion","html_url":"https://github.com/taion","followers_url":"https://api.github.com/users/taion/followers","following_url":"https://api.github.com/users/taion/following{/other_user}","gists_url":"https://api.github.com/users/taion/gists{/gist_id}","starred_url":"https://api.github.com/users/taion/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/taion/subscriptions","organizations_url":"https://api.github.com/users/taion/orgs","repos_url":"https://api.github.com/users/taion/repos","events_url":"https://api.github.com/users/taion/events{/privacy}","received_events_url":"https://api.github.com/users/taion/received_events","type":"User","site_admin":false},"created_at":"2016-03-14T16:33:42Z","updated_at":"2016-03-14T16:33:42Z","body":"I think you _have_ to do something like that, though. Otherwise there's no way for a component to know which route context it belongs to. By construction, history can't do that, because history is on the document level."}}