Open yeoshuheng opened 2 months ago
This has already been added to planned enhancements.
Team chose [response.Rejected
]
Reason for disagreement: I disagree with this judgement as the issue here is not with specificity, but rather it is delivering the user getting an message for a different error. (alphanumeric but the problem is with the spacing of the tag variable)
Additionally, if we look at the full section for your planned enhancements, you are talking about editing "field that has not changed / has nothing to remove", this is different from the current issue brought up abeit a similar sounding title.
Have added a screenshot from your DG for reference.
Hence I would like to caution and bring up the issue that there is insufficient work planned to resolve such issues and that the development team should not dismiss this.
This is the given parameter constraint in the UG.
Might be good for the error message to align to what is written in the UG, as a user, I would not be able tell specifically that the problem is with my spacing from the given error message.