Open minreiseah opened 2 months ago
For the current version we decided on task
because it is shorter and does not cause any clashes with other existing functions for this version. If we chose to use addtask
then we would have to change add
to addemployee
if we follow this argument.
Considering that our options were task
and add
or addtask
and addemployee
for the sake of optimizing typing speed for the current version we opted for the 2 shorter commands.
Additionally, the name of the command is not a priority issue compared to getting the different features working. Should the users prefer to use a different command word, it can be easily changed.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
When adding an employee, we use
add
. However, when adding tasks, we usetask
. This difference in semantics could confuse users who are used to other CMSs that standardize the naming.addtask
might be more appropriate here.