{"action":"closed","issue":{"url":"https://api.github.com/repos/cs2103aug2015-f11-2j/main/issues/39","labels_url":"https://api.github.com/repos/cs2103aug2015-f11-2j/main/issues/39/labels{/name}","comments_url":"https://api.github.com/repos/cs2103aug2015-f11-2j/main/issues/39/comments","events_url":"https://api.github.com/repos/cs2103aug2015-f11-2j/main/issues/39/events","html_url":"https://github.com/cs2103aug2015-f11-2j/main/issues/39","id":105950876,"number":39,"title":"Parsing implementation","user":{"login":"wryyl","id":409724,"avatar_url":"https://avatars.githubusercontent.com/u/409724?v=3","gravatar_id":"","url":"https://api.github.com/users/wryyl","html_url":"https://github.com/wryyl","followers_url":"https://api.github.com/users/wryyl/followers","following_url":"https://api.github.com/users/wryyl/following{/other_user}","gists_url":"https://api.github.com/users/wryyl/gists{/gist_id}","starred_url":"https://api.github.com/users/wryyl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wryyl/subscriptions","organizations_url":"https://api.github.com/users/wryyl/orgs","repos_url":"https://api.github.com/users/wryyl/repos","events_url":"https://api.github.com/users/wryyl/events{/privacy}","received_events_url":"https://api.github.com/users/wryyl/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cs2103aug2015-f11-2j/main/labels/type.task","name":"type.task","color":"006b75"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-09-11T06:10:12Z","updated_at":"2015-09-13T07:21:32Z","closed_at":"2015-09-13T07:21:32Z","body":"#### Keywords:\r\n\r\n##### Priority\r\n\r\npriority: `priority <level>`\r\n\r\n##### Dates\r\n\r\nstartDate keywords: `from`, `start`, `begin`\r\nendDate keywords: `due`, `by`, `to`, `end`\r\n^ Note: Generally can mix and match, but `to` should not be available as a standalone keyword. For instance:\r\n\r\n- `add <task> from <date> to <date>` - yes\r\n- `add <task> from <date> end <date>` - yes\r\n- `add <task> start <date> due <date>` - yes\r\n- `add <task> due <date>` - yes\r\n- `add <task> by <date>` - yes\r\n- `add <task> to <date>` - **no**\r\n\r\n##### Tags (not v0.1)\r\n\r\nPrefix any word (except first word) with `#`. Probably should disallow dates to be tagged as well.\r\n\r\n#### Examples of commands and the resultant parsed values:\r\n\r\n- **`add do cs2103 tutorial priority high`**\r\n\r\ncontent: `do cs2103 tutorial`\r\npriority: `high`\r\n\r\n---\r\n\r\n- **`add do cs2103 tutorial priority high due tomorrow`**\r\n\r\ncontent: `do cs2103 tutorial`\r\npriority: `high`\r\nendDate: `<tomorrow's date>`\r\n\r\n---\r\n\r\n- **`add attend cs2103 tutorial priority high from 11/9/2015 11am to 12pm`**\r\n- **`add attend cs2103 tutorial from 11/9/2015 11am to 12pm priority high`**\r\n\r\ncontent: `attend cs2103 tutorial`\r\npriority: `high`\r\nstartDate: `11/9/2015 11am`\r\nendDate: `11/9/2015 12pm`\r\n\r\n---\r\n\r\n- **`add do homework with priority high after school from 11/9/2015 5pm to 8pm`**\r\n\r\ncontent: `do homework with priority high after school`\r\nstartDate: `11/9/2015 5pm`\r\nendDate: `11/9/2015 8pm`\r\n\r\nPriority is not set because it's actually part of the content. i.e. cannot just do a search for `priority <high | medium | low>`. Have to make sure it's defined at the end of the task, next to other keywords.\r\n\r\n**Is this ideal?**\r\n\r\n---\r\n\r\n- **`add do #homework with priority high after #school from 11/9/2015 5pm to 8pm`**\r\n\r\ncontent: `do homework with priority high after school`\r\nstartDate: `11/9/2015 5pm`\r\nendDate: `11/9/2015 8pm`\r\ntags: `['school', 'homework']`\r\n\r\nTags can be defined at any point in the task, by prefixing the word with `#`."}}