Open ruiyangzh opened 12 months ago
As per the UG, this is expected behaviour, so the type has been changed to a FeatureFlaw
In addition, the team posits that the behaviour is logical & likely to be expected:
edit
command is introduced to the user as editing the values at the index.edit
command currently reports that the edit was successful (To our knowledge, the question of whether edit
should accept such inputs was raised in another bug report as a separate issue)edit
operation was successful, and that something was edited.
John
, the edit John
==> John
was made. edit
operation would update the Last Modified Date Time field.
edit
command updates the field upon successful execution.Hence, the current behaviour is, if you assume that leaving Last Modified un-edited is also reasonable, at worst an arbitrary decision between two reasonable alternatives (as per the reasonable-ness argument in point 4.).
However, the team posits that it is in fact more likely that, given the other factors, that the current behaviour is in fact more reasonable.
Hence, the team puts forth the idea that the current behaviour is not a FeatureFlaw
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
One would expect editing without changing any details to count as not being 'modified'. However this is not true in the current version.
See:
Before:
After: