Open leroytan opened 2 weeks ago
Rejected, severity medium doesn't really make sense here either.
It is meant to be a summary for commands after users read through the UG.
Additionally, we split the command words as well in the features section and did not use the short form command in the format part.
Team chose [response.Rejected
]
Reason for disagreement: Thank you for your response.
Firstly, there is no guarantee that users will read through the entire User Guide (UG) in order. The table of contents allows users to jump directly to specific sections. For instance, a seasoned developer might only refer to the Quick Start and Command Summary sections, while regular users might rely heavily on the Command Summary, as it’s challenging to memorize 30 commands.
Secondly, while other parts of the UG correctly separate long and short forms of commands, this does not negate the issue in the Command Summary. Just because the commands are presented correctly elsewhere does not make the issue in the Command Summary less confusing.
The use of slashes here remains misleading, as it serves two different purposes. This inconsistency can confuse users, regardless of the correctness in other sections of the UG.
Given these considerations, I would like to retain this as a bug.
Thank you for your understanding.
The use of slashes here \/ is confusing, it is used to mark short and long form commands, as well to mark the labels that is allowed in the command. In the worst case the user may never be able to run a command at all.