Incorrect error messages for update command regarding missing / invalid index

[thant]

As seen in the screenshot, the error message tells the user that no field to update is specified, instead of the error being regarding the invalid index. Whilst I agree that there being no field to update is also a valid error, I believe when no flags are specified and index is invalid/ missing, the error message should be focused upon the index first and foremost.

As seen below, even if I omit the index entirely, the same error message appears. Then, following the error message and adding in the field, I am finally presented with the respective index format error.

Also, it would be good to indicate to enter the index before any flags, since this is absent from help --update. If i then enter an index after the fields to be changed, the error message should be flagging up the command format being incorrect instead of the index not being in range.

[soc-pe-bot]

Team's Response

Thanks for the notice! The error output can indeed be improved. We changed the severity though as it doesn't cause major discomfort to the user and the errors are still handled gracefully (even though not so specifically as they can be).

Items for the Tester to Verify

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

• I disagree

Reason for disagreement: [replace this with your explanation]

---