Open sethteo opened 2 months ago
Our app currently reads S/
as a prefix for status as mentioned in the user guide. Hence the error message is correct as the input is being read as containing input for a second invalid status O Usul
.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
I tried adding an interviewee with a name that contains "/" however the error provided tells me that the status is wrong when I gave a correct status
command used: add -a h/My Article d/01-01-2024 s/draft i/Saravanan S/O Usul