Specialisation field does not accept all non-empty fields

[alvinlim277]

Particularly if the user input matches an existing field prefix like in the example below:

[soc-pe-bot]

Team's Response

This is a limitation of a CLI app and is very difficult to fix because the string input may contain other valid prefixes, which need to be parsed by the parser. It is a very rare user input that specialisation contains a valid prefix surrounded by whitespace, so the potential benefit that the fix offers the user is very low compared to what our v1.4 currently offers. However, we do acknowledge that there may be temporary workarounds for this issue. For example, update the REGEX for specialisation to disallow /. Another workaround is to specify clearly in the user guide that the command may not work as expected if the input contains a valid prefix surrounded by whitespace.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---