soc-pe-bot
commented
5 months ago Team's Response
Expanding range of valid characters is a planned enhancement. Scenario that s/o can lead to an invalid capture of stars has known and intended behaviour
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Names does not allow for non alphanumeric
Expect names to be able to take values like ' as it can be used is some cases. Current app does not allow such names.
[original: nus-cs2103-AY2324S2/pe-interim#4643] [original labels: severity.Low type.FeatureFlaw]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Hi thanks for the bug report,
We recognise that the app currently only allows for alpha-numeric characters in the name, and that can be a little restrictive.
Hence, we have specified that there is already a Planned Enhancement to increase the range of allowed characters for the name.
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)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
When adding someones names one might want to use "s/o" but currently the app mistakes that for the prefix for starts