{"action":"created","issue":{"url":"https://api.github.com/repos/jmhobbs/jsTodoTxt/issues/10","repository_url":"https://api.github.com/repos/jmhobbs/jsTodoTxt","labels_url":"https://api.github.com/repos/jmhobbs/jsTodoTxt/issues/10/labels{/name}","comments_url":"https://api.github.com/repos/jmhobbs/jsTodoTxt/issues/10/comments","events_url":"https://api.github.com/repos/jmhobbs/jsTodoTxt/issues/10/events","html_url":"https://github.com/jmhobbs/jsTodoTxt/issues/10","id":179757603,"number":10,"title":"Support arbitrary extensions","user":{"login":"smichel17","id":6563664,"avatar_url":"https://avatars.githubusercontent.com/u/6563664?v=3","gravatar_id":"","url":"https://api.github.com/users/smichel17","html_url":"https://github.com/smichel17","followers_url":"https://api.github.com/users/smichel17/followers","following_url":"https://api.github.com/users/smichel17/following{/other_user}","gists_url":"https://api.github.com/users/smichel17/gists{/gist_id}","starred_url":"https://api.github.com/users/smichel17/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smichel17/subscriptions","organizations_url":"https://api.github.com/users/smichel17/orgs","repos_url":"https://api.github.com/users/smichel17/repos","events_url":"https://api.github.com/users/smichel17/events{/privacy}","received_events_url":"https://api.github.com/users/smichel17/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-09-28T12:22:46Z","updated_at":"2016-09-29T19:12:18Z","closed_at":null,"body":"Rather than just having support for hidden and due extensions and adding additional extensions as they are requested, we could add an `extensions` data member that is an array/object using key:value pairs, where the key is the extension and the value is an array of values for that extension\r\n\r\nSo, `example task dep:1 dep:2 h:1` would parse to\r\n```\r\n{ text: \"example task\"\r\n  extensions: { dep: [ '1', '2' ]\r\n                h: [ '1' ]\r\n              }\r\n}\r\n```\r\n\r\nIt allows anyone using the jsTodoTxt to implement their own custom extensions without building in behavior that breaks the todo.txt standard (or having to do other people's work for them, if they want to use this to parse tasks and support their own custom extension)."},"comment":{"url":"https://api.github.com/repos/jmhobbs/jsTodoTxt/issues/comments/250562949","html_url":"https://github.com/jmhobbs/jsTodoTxt/issues/10#issuecomment-250562949","issue_url":"https://api.github.com/repos/jmhobbs/jsTodoTxt/issues/10","id":250562949,"user":{"login":"jmhobbs","id":115059,"avatar_url":"https://avatars.githubusercontent.com/u/115059?v=3","gravatar_id":"","url":"https://api.github.com/users/jmhobbs","html_url":"https://github.com/jmhobbs","followers_url":"https://api.github.com/users/jmhobbs/followers","following_url":"https://api.github.com/users/jmhobbs/following{/other_user}","gists_url":"https://api.github.com/users/jmhobbs/gists{/gist_id}","starred_url":"https://api.github.com/users/jmhobbs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jmhobbs/subscriptions","organizations_url":"https://api.github.com/users/jmhobbs/orgs","repos_url":"https://api.github.com/users/jmhobbs/repos","events_url":"https://api.github.com/users/jmhobbs/events{/privacy}","received_events_url":"https://api.github.com/users/jmhobbs/received_events","type":"User","site_admin":false},"created_at":"2016-09-29T19:12:18Z","updated_at":"2016-09-29T19:12:18Z","body":"> What kind of deeper parsing are you thinking of?\r\n\r\nNo clue!  Just wondering if it was a thing.\r\n\r\n> <key>:<value> is the format for add-ons in the todo.txt spec. I\r\n\r\nIn that case, yes, we should support it explicitly.\r\n"}}
{"actor":{"display_login":"jmhobbs"}}