search

jamieeeleow / pe

0 stars 0 forks source link

Error when keying in a valid input #8

Open jamieeeleow opened 1 year ago

jamieeeleow commented 1 year ago

From my command as seen in the image, my telegram handle input fits the criteria for valid input but instead I was being thrown an error message.

  1. Started with the "@" symbol
  2. Contains only alphanumeric characters
  3. Only other symbol is underscore which is allowed
  4. At least 5 characters long

image.png

However, my input was flagged as invalid.

nus-pe-bot commented 1 year ago

Team's Response

Firstly, this should not be triaged as a High severity issue, because "only problems that make the product almost unusable for most users should have this label." (from CS2103 website).

This is a duplicate of the issue "#2950: Invalid description for the telegram handle input" because both talk about telegram handles not exhibiting the advertised behaviour.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Invalid description for the telegram handle input

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

image.png

It is mentioned in the UG that underscores are allowed in telegram handles but when testing it out in the app itself, it is noted that having underscore will result in an error message as shown below.

image.png

[original: nus-cs2103-AY2223S2/pe-interim#3881] [original labels: severity.High type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Thank you for your input. We will take this into consideration for the future. However, we believe that this issue does not warrant a High severity as the app still works fine despite this, and "only problems that make the product almost unusable for most users should have this label." (CS2103 website). We propose a change to Medium severity instead.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.High`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]