Open yeoshuheng opened 2 months ago
The behaviour of entering the w/
prefix with no value has been documented in the UG.
Explaining this everywhere that it is relevant would be needlessly repetitive.
Team chose [response.Rejected
]
Reason for disagreement: I believe that this is important, since the table acts as a quick lookup. Something like this would be confusing and unintuitive for users who expect to be able to do a quick lookup, but end up being confused and having to go through the UG again.
Within the parameter constraints table, we talk about 0 values being treated as 'w/'.
However, what does w/ entail? Might be good to go into more detail here, especially since I can see users using this UG's table as a quick lookup as they use fitbook. This might lead them to have to scour the UG more.