Open avielcx opened 1 year ago
We have already specified in the UG that certain commands with no effect can still be executed, but we may improve this in the future by displaying an error message instead.
Team chose [response.NotInScope
]
Reason for disagreement: I am sure that the UG's primary purpose is not to act as a mere safety net or insurance for the developer team to cover imperfect features.
Furthermore, while the feature flaw acknowledgement was mentioned in the UG, it does not change the fact that it is a feature flaw.
Having so many redundant commands makes the program heavy and repulsive, especially to new users (possibly programming inexperienced), as they constantly have to trial and error to decide what is redundant and not.
As per the developers' acknowledgement, it will be good to remove redundant features.
As such, given the impact of redundant features and further confirmation from the developers, it is, without a doubt, a feature flaw.
It will be good to check first whether or not the tag exist, before deleting. An exception can be raised if the tag doesn't exist in the first place.