Open jeromeongithub opened 1 year ago
There are no such restrictions; input can be anything. However, you can define the format of the command (e.g., using only / as the separator)
@okkhoy . Hi Prof, could clarify your statement above? How do we deal with inputs meant to append to the list but involve the word "mark" and "unmark"?
Again, same thing -- no restrictions that say "keywords" should not/cannot appear in the description
so you have inputs such as: todo mark papers
or add todo mark papers
@okkhoy what if keywords appear at the start, such as mark papers
?
it is still a valid input 🙂 ps: you could constraint the input to say no keywords in the beginning, which is acceptable
There are no such restrictions; input can be anything. However, you can define the format of the command (e.g., using only / as the separator)
Can I confirm, this means we can specify input to be in the format like: /todo taskname
so it's easier to identify an input?
yes you can. (pls document it in the user guide clearly)
@okkhoy Basically, if I understand this discussion correctly, this means we can define the input in any way we want, as long as the user can perform the actions defined in each level. Am I correct?
Yes. That is correct.
Can we assume that there won't be tasks like "mark papers" which start with "mark"/"unmark"?