Task #3655

Bug #4924: [SDKs] Improve arv edit error handling UX

[SDKs] "arv edit" should not fail just because some special attribute (which I didn't edit) is rejected by the "update" call.

Added by Tom Clegg almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
SDKs
Target version:
Start date:
01/07/2015
Due date:
% Done:

0%

Estimated time:

Description

Possible ways to improve:
  • Do not include unchanged attributes in the "update" API call.
    • This fixes the bug only in the cases where the user doesn't happen to edit any uneditable attributes.
  • When the discovery document does provide information about which fields are permitted in an update, and the user changes stuff that isn't in the schema, volunteer to omit those changes from the update.
  • Have the discovery document provide information about whether fields are editable or not. Do not present the non-editable fields for editing. See #3818
    • It might be desirable to see those readonly attributes, though. Perhaps they could be shown in an ignored/comment block before or after the editable JSON, much like the instructions provided by "git commit"?

History

#1 Updated by Peter Amstutz over 5 years ago

  • Description updated (diff)

#2 Updated by Peter Amstutz over 5 years ago

  • Description updated (diff)

#3 Updated by Tom Clegg over 5 years ago

  • Description updated (diff)
  • Category set to SDKs
  • Target version set to Arvados Future Sprints

#4 Updated by Tom Clegg over 5 years ago

  • Tracker changed from Bug to Task
  • Parent task set to #4924

#5 Updated by Peter Amstutz over 5 years ago

  • Description updated (diff)
  • Assigned To set to Peter Amstutz

#6 Updated by Peter Amstutz over 5 years ago

  • Status changed from New to In Progress
  • Start date set to 01/07/2015

#7 Updated by Peter Amstutz over 5 years ago

  • Status changed from In Progress to Resolved
  • Remaining (hours) set to 0.0

Also available in: Atom PDF