Optimization of CLI for add Feature

[BryanL2303]

For the add command there are 2 required parameters tag and housing type which are limited to a few available options as seen below.

Since a focus of the project is to achieve higher speed with typing, it makes sense to create a shorter form of input so that the user does not need to type out the whole option.

e.g. Instead of t/Buyer or t/Seller we could have t/b or t/s.

This makes a bigger difference for the housing type for users who needs to type out GOOD CLASS BUNGALOW multiple times. They would also have to correct their mistake if they type the line wrongly.

Since we already created short forms for the tags, as in t/ instead of tag/ I think it only makes sense to do so as well for fixed constraints like this.

[soc-se-bot]

Team's Response

Thanks for raising this issue.

We downgrade the severity to low as this does not cause a occasional inconvenience to users as its just a single field.

Furthermore, we believe fixing this issue is deemed less important than the work done to implement the other features that include, adding, editing and filtering clients based on their housing types.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

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

---