Open teojunda opened 4 months ago
Not a valid bug at all. There is no right place to add this consolidated table.
Too early and users will not understand what it's about. Too late and users might have already input something wrong by the time they scroll to the bottom of the user guide.
Team chose [response.Rejected
]
Reason for disagreement: > Not a valid bug at all. There is no right place to add this consolidated table.
Too early and users will not understand what it's about. Too late and users might have already input something wrong by the time they scroll to the bottom of the user guide.
Readers would appreciate having a consolidated table of parameter constraints placed after the summary of commands. Many readers do not read the user guide in chronological order. Instead they jump from section to section based on what they are interested in. Therefore, it is not a big deal even if the information is provided early. Readers will eventually understand it.
By repeating the constraints of the same parameter in different sections, it makes the user guide unnecessarily long and forces the reader to read the same content over and over again. This confuses the reader as it makes it "hard to see what's similar and what's different" (see below) between the different sections. This hinders the readability of the user guide.
The constraints for phone number field is repeated in
add
andedit
commands. It will be more helpful to have a consolidated table describing the constraints of all parameters. Otherwise, it is difficult for the reader as there is a lot of repetitive content to read through.