search

crabnuggets / pe

0 stars 0 forks source link

Posting certain comments can result in cOOPer requesting for unexpected results #7

Open crabnuggets opened 2 years ago

crabnuggets commented 2 years ago

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).

image.png

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

image.png

nus-se-bot commented 2 years ago

Team's Response

Based on the format specified in the User Guide, using /on will treat whatever comes after it as the argument. The '/' symbol is reserved for command parsing.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Thank you for your response. However, I do have to respectfully disagree with the team's justification provided because the restrictions on user input in the team's response do not seem to be made clear in the UG. I did make another quick scan of the UG to make sure of this (paying particular attention to the cOOPer's Commands section as that seems to be the most probable section where such information is located) but I could not find any mention of the '/' symbol being reserved for parsing. In addition, it seems that even if /on or the '/' symbol were to be reserved for the command, the additional prompt seems to be unexpected as based on the user guide, it seems that the prompt ("Please enter a positive integer...") is usually printed when the user is in the process of creating balance sheet/cash flow statements. The screenshot below should also hopefully verify that the prompt for a positive integer in the original report is not requesting for the index of a forum post:

image.png

However, I do also acknowledge that the original issue posted can be circumvented by the user if the user had just placed an additional character before /on (e.g. something like sadf/on would not result in the issue) so this should not cause any significant issues to a user, even though the error produced can be confusing.