It makes sense for commands with optional or multiple inputs to have separators to help parse through commands, but totalexpense has only 1 parameter which is compulsory anyway, so it does not make sense to need a separator which just complicates the input more than necessary.
Thanks for pointing this out but the reason we decided to use the separators is so that inputs are more consistent for all functions so as to not confuse users.
It makes sense for commands with optional or multiple inputs to have separators to help parse through commands, but totalexpense has only 1 parameter which is compulsory anyway, so it does not make sense to need a separator which just complicates the input more than necessary.
[original: nus-cs2113-AY2324S2/pe-interim#927] [original labels: severity.Low type.FeatureFlaw]