[T7][T10-C1] #69
[T7][T10-C1] #69
Conversation
docs/UserGuide.md
Outdated
|
|
||
| >Format: **Add** <index> #tag1 #tag2 | ||
|
|
||
| Example: Add E1 #win #victor #finally |
There was a problem hiding this comment.
Can't I add the tag when I am adding the task? If No, then take note that your add tag process continues for two commands..which is not too good right? Why can't you make it an optional parameter in the add command
There was a problem hiding this comment.
ok noted. we have already done that but not stated specifically in the user guide under add.
this function is for user to add additional tags
docs/UserGuide.md
Outdated
|
|
||
| >Format : **Add** [<event description>; <date(DDMMYY)>; <start time>; <end time>] | ||
|
|
||
| Example: Add [Sam's birthday party; 20/12/16 ; 9pm] |
There was a problem hiding this comment.
Why should Jim use a square bracket for events and not for other task types?
Consistency is good to get users on board.
There was a problem hiding this comment.
we wanted to add a square bracket to differentiate between deadline and event/event and todo since those two may overlap. ie. event can only have a start time but not an end time or the other way around which the program might mistaken it for a deadline.
docs/UserGuide.md
Outdated
|
|
||
| >Format: **Add** <deadline description>; <date(DDMMYY)>; <end time> | ||
|
|
||
| Example: Add complete report; 120916; 1900 |
There was a problem hiding this comment.
So you are supporting multiple date/time formats? (above its different.) Please mention this explicitly.
There was a problem hiding this comment.
ok. we will make the changes. our task manager can only add according to this format currently.
docs/UserGuide.md
Outdated
|
|
||
| ####2.1 Edit all task details in one go | ||
|
|
||
| >Format: **Edit** <index> [<event description>; <date>; <start time>; <end time>; <tags>; !] |
There was a problem hiding this comment.
Whats the exclamation mark? How do I add it in first place?
There was a problem hiding this comment.
it is for marking priorities so it should be added after the tags
docs/UserGuide.md
Outdated
|
|
||
| >Note: Removing start time from events will automatically convert them into deadlines. | ||
|
|
||
| >Note: Removing end time from deadlines will automatically set the end time of the deadline to 2359. |
There was a problem hiding this comment.
that is a good comment. Appreciated!
docs/UserGuide.md
Outdated
|
|
||
| >Format: **Edit** <index> **end** <end time> | ||
|
|
||
| Example: Edit E1 end 1900 |
There was a problem hiding this comment.
If any of the keywords like end show up in the description make sure to handle it.
docs/UserGuide.md
Outdated
|
|
||
| > Format: Done <index>-<index> | ||
|
|
||
| > Format: Done <index>, <index> |
There was a problem hiding this comment.
Good. Make sure to handle cases like T1-E3
docs/UserGuide.md
Outdated
|
|
||
| >Format: **Delete** <index> #tag1 #tag2 | ||
|
|
||
| Example: Delete E1 #win #victor #finally |
There was a problem hiding this comment.
How is this different from editing a tag? Looks a bit inconsistent to add this to delete.
There was a problem hiding this comment.
do you mean that
Edit D1 #doOrdie > #101
can be changed to
Edit E1 #win #victor #finally
which will delete the tags?
in a sense it will make the edit function more flexible but it may confuse the user since they will take edit as pure editing and will it not be defying the SRP?
|
Hi guys, The user guide looks much better now apart from few inconsistencies here and there. Take note of the things I have mentioned here. |
No description provided.