The name field doesn't support certain special characters such as / in S/O which is quite common in real life. But at the same time it allows the name totally consisting of numbers, which doesn't conform to the common sense.
NotInScope - Addressed the S/O as being invalid for now in the UG and for a future implementation. As for name consisting of numbers we allow this for flexibility (take for instance Elon Musk's son?)
The name field doesn't support certain special characters such as / in S/O which is quite common in real life. But at the same time it allows the name totally consisting of numbers, which doesn't conform to the common sense.
[original: nus-cs2103-AY2324S2/pe-interim#5552] [original labels: severity.Low type.FeatureFlaw]