crabnuggets / pe Goto Github PK

Given that the user can only indicate the start of the hour for his/her available time, it seems unnecessary for the user to indicate the minutes of the hour when setting his/her availability.

With at least one post on the forum panel, inputting the following seems to produce unexpected results (program requests for a positive integer argument which is immediately rejected).

Supposing this argument is for the forum post index, inputting 1 does not seem to be accepted either:

In page 22 of the DG, SignInDetailsParser seems to be missing its own activation bar.

The user is able to set availability dates that have already passed.

Manual testing instructions in the DG indicate the use of a comma to separate the username from the /pw flag:

However, the actual log in input requires no commas, and produces an error if a comma is used (albeit the example command in the help message printed on startup involves no use of commas):

Really trivial, but some lists (e.g. in page 16) start off with an uncapitalized letter:

For example, entering list garbage input will pass as a valid command in cOOper. This perhaps might be a part of the intended design (e.g. to allow for potential typos by the user) but it seems that this is not as consistent in some parts of the program. For example, when generating cf projections, garbage input after a valid input command (e.g. proj 5 garbageinput) is not negelected:

After a meeting is scheduled, it seems the case (and intuitively so) that both parties involved in the meeting will no longer be available on that particular date/time. However, their new availabilities after the meeting has been scheduled is not updated in the output using the availability command. This might be confusing for users with even more meetings scheduled as it is difficult for them to identify the source of the conflicting schedule.

There seem to be potential missing dotted line arrows for the sequence diagram for Logging in. Even though the method calls might return void, it seems like VerificationUi should have a dotted-line returning back to :Login for each method call made by :Login.

Similarly, dotted line arrows from :Verifier to :Login seem to be missing after each Set method call by :Login in the alt block.

Entering list will print out the balance sheet as intended. However, if whitespace(s) are input before the command (e.g. in the event of a minor typo by the user), cOOPer is unable to understand the desired command input by the user:

The same applies to most, if not all, other inputs by the user as well (e.g. not able to accidentally add whitespace before input).