Open niekis opened 1 year ago
Thank you for raising this, however, we believe this is more of a preference than a suggestion.
The standard convention for tags in general is to not allow spaces. We have similarly adhered to AB3's design. Although we understand from your perspective it might be reasonable, we believe this is an issue of preference and more of a suggestion than an actual flaw.
Furthermore, we are following standard coding conventions as seen below.
Team chose [response.Rejected
]
Reason for disagreement: Thanks for the response!
Apologies, but I don't understand how standard coding conventions (especially regarding tags in XML) would affect the User's expectations while using the application. In the case of XML, tag
actually refers to code related terminology. In constrast, for the case of the application, tags
refer to a piece of information tagged to a person.
It is unusual that certain fields (i.e address and name) can take in whitespace and dashes, while tags are unable to.
This might be inconvenient for some users under certain circumstances. For instance: in the UG, athletes were tagged with names of sports as an example.
Therefore it seems quite reasonable to tag an athlete as a player of table tennis
which has two words, or at least as table-tennis
. However, the current implementation of tags
hinders the user from saving it in this way and can be considered as undesirable behavior (i.e. a feature flaw), or at least inconvenient while they have to figure out a new way of saving such information.
Tag does not allow whitespace or dashes which are resonable for a user to want to add