As seen in the before and after screenshots, Maria s/o Hughman Patrick is shortened to Maria and the rest of the end after s/ is saved as a skill. This invalid parsing could be due to "s/o". The parsing/validation of name should allow for these characters among others e.g. "d/o" as there is a high likelihood these names will be added at some point in time given how this is an app that manages jobs.
Overall, it would be good to allow these names to be added in full by allowing the parser/validation to be more flexible. One could modify the parsing character for skill to be something other than "s/" such as "sk/" or attempt to validate this name while keeping the "s/" identifier.
Before (the command is input)
After (the command is input)
After (the command is input) - rest of name is saved as skill
Input: edit 3 n/Maria s/o Hughman Patrick
As seen in the before and after screenshots, Maria s/o Hughman Patrick is shortened to Maria and the rest of the end after s/ is saved as a skill. This invalid parsing could be due to "s/o". The parsing/validation of name should allow for these characters among others e.g. "d/o" as there is a high likelihood these names will be added at some point in time given how this is an app that manages jobs.
Overall, it would be good to allow these names to be added in full by allowing the parser/validation to be more flexible. One could modify the parsing character for skill to be something other than "s/" such as "sk/" or attempt to validate this name while keeping the "s/" identifier.
Before (the command is input)
After (the command is input)
After (the command is input) - rest of name is saved as skill
[original: nus-cs2103-AY2425S1/pe-interim#332] [original labels: severity.Medium type.FunctionalityBug]