pyk595 / ped Goto Github PK

Tags are can be created during add and edit commands. However, there are no other features for tags. Is it necessary to have the tags in that case? You can either consider writing more about tags in the documentation or removing them entirely.

Adding of new tasks documentation is misleading. In the table it shows 4 digits but in the prose it says 2 digits, you can consider changing to 2 digits instead

Target user and value proposition is not specified clearly enough, users might not know what we are able to do with the product from the start

In your user guide you used n\Hans bo

Unfortunately, these commands don't actually work with the \, maybe you can consider changing them?

The format for the command is correct, however the returned message seems to say otherwise. This occurs when I use negative number of 0 as index.

When copy pasting the sample command for add, the formatting for text is off, make sure to check your spacing for the other commands as well

The undo feature seems to promise that it will undo the effects of add. Assuming an unknowing user opens the jar with faulty data and accidentally overwrites the file, when they reference the guide and see the undo feature, they will expect that the effect of overwriting the data file is undone.

To recreate what I've done, I deleted a description field in the task.json and loaded the jar, then I wrote an entry for a new task and ran undo, before checking my contactlist.json

I'm not sure if you can still change the behaviour but if you can, you should really create a backup of the files on a read error. I personally feel the part where all 3 json files are overwritten is not the intended behaviour but I will give benefit of doubt and just write one feature flaw.

The help feature is still referring to the ab3, so is the copy url. Remember to change it C:

This seems to imply that the mod is tagged to the group. However, when I set default group for a mod and I edit person to have that mod, the person does not automatically swap to that group. This is a feature flaw, but I believe you can change your documentation to define the scope of the "Helps prevent users from repeatedly entering the same data." statement.

Low testability because users might not be using the default mail app on their computers or they do not have a sample csv file to use.

You can consider adding a sample csv fiile here so your testers can have something to work with. Hope you can fix this!

Quick start doesn't tell me that I need the default email app to use with the mail type commands. Perhaps you can talk about it?

I believe this is a feature flaw but I'll just list it as a functionality bug so you can change it. tasks past the deadline should not be able to be added because the date has already passed

Language error in user guide exit command. Consider changing to "no unforeseen errors have occurred"

Contact cards don't have descriptors, first time users will be confused by which fields are which, you can add a label

If text overruns for task, it gets truncated and users are unable to see the tasks, as you can see from the above screenshot where I padded with filler 'a' characters

Assuming a user needs to input more information, there is no reasonable way for them to see the details via the gui.

The mail-x feature is a little ambiguous when it comes to what I can use it with. You can consider stating that all other categorisation types are not supported?

Help promises that as long as you have a valid command word, the help function will tell you how to use it. This is not the case for newTask.

This description is ambiguous. I tested with one faulty json file and I lost data for all 3 json files. You might want to be more specific on the magnitude of the data loss.

You can consider giving a CLI command alternative because it is meant to be optimised for CLI input

Formatting error in sample command for help find