yuxianglim
commented
4 years ago Team's Response
As per requirement and as a CLI user, most will be able to identity the input and output easily. As most of bug catcher are not CLI base user, naturally it might be challenging at the start to get use to the commands input and outputs. However this does not affect the usability of the program.
As for the next line issue, there are certain parts of the program that we feel that an empty line would serve the user better and some which we think it would be without. Also, this does not affect any functionality by itself and it depends on user preference too. As having too many empty lines would result in user having to scroll through many lines to check through their previous inputs too. Thus it might actually be a double-edged sword.
However, if required, we can always add a next line to all outputs to satisfy the "OCD"s and make the messagebank more unify. This can be done easily if ever required.
Duplicate status (if any):
--
Description: Sometimes there will be an empty line after one command finishes. Most of the time there will not have an empty line.
Current Bahaviour:
Advice: I would prefer a prgram which has unified UI format. I would also be able to clearly identify which part is my command and which part is the program's output. However, current display may not do it.
[original: nus-cs2113-AY1920S2/pe-interim#696]