lyskevin / ped Goto Github PK

The list-members command works even with extra arguments being passed into it. A way to fix this would be to check for exact string equality with “list-members” after trimming any preceding and trailing whitespace from the command. The same goes for list-inv and list-tasks.

The done command gets autocompleted to the set-deadline command.

The calendar command does not work even though it is listed in the user guide. The team can consider removing it from the user guide (if it is no longer being implemented) since it could lead users to think that there is a bug in the software when in reality the feature does not exist.

I tried to execute the command in the above image from the list-tasks screen, but got feedback that the task didn't exist under the specified member, even though it shows the member with ID GS under the task at that task index.

Upon switching to the list-members screen, that task is not listed under the member with that specified ID. It seems like there is a deviation between the list-members and list-tasks views. The team might want to consider checking the part of the code which handles task mapping to ensure that all views get updated when new tasks are assigned to members.

The tn/ tag is mapped to image url and the im/ tag is mapped to task name in section 3 of the user guide. Looks like they should be swapped around.

A member's name gets truncated if it is too long. The fix should be pretty similar to the one in Duke where long commands/reponses were also getting truncated. A possible fix is to use the setWrapText method or the wrapText attribute in FXML.

User guide documentation

Application feedback

The deadline command does not work even though it is listed in the user guide. It seems that it has not been implemented since it does not come up in the autocomplete feature. I tried the example deadline command that is documented in the user guide but it did not work.

Application feedback

User guide documentation

The add task syntax is documented wrongly in section 3.3.1 of the user guide. The parameters should be given as tn/NAME s/STATUS tt/TAG (feedback from the application) but are listed as t/TASK_NAME s/STATUS t/TAG in the user guide.

The optional parameters work as expected (they need not be given to add a task successfully) but the user guide should be updated to reflect the prefix for the task name to be tn/ instead of t/. Furthermore, the tag prefix should also be updated to tt/ instead of t/. Having t/ as the prefix for both task name and tag in the user guide could lead to some confusion among users.

I tried the assign-member ti/1 mi/AS command under the quick start section but it didn’t work. It looks like the syntax was updated sometime after the quick start section was written and the syntax in that portion of the user guide was overlooked. The updated command syntax works correctly so it’s probably just a matter of updating the Quick Start section of the user guide.

The first image shows the result of copying the assign member command from the quick start section of the user guide.

The second image shows that the command works with the updated syntax.

Medium severity since it is the example command given at the very start of the user guide.

As stated in the title, the calendar command image is missing in section 3.1.2 of the user guide.