Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Won't Do
-
Affects Version/s: None
-
Fix Version/s: 1.3.0
-
Labels:
-
Template:customfield_11100 18322
-
Story Points:5
-
Development Team:Spitfire
Description
When we make a PUT request to update a managed pacakge: /eholdings/packages/583-4345, with the request body below:
when "isSelected" is false:
{
"data": {
"type": "packages",
"attributes": {
"isSelected": false,
"visibilityData": {
"isHidden": false
},
"allowKbToAddTitles": false,
"customCoverage": {
"beginCoverage": "2018-08-13",
"endCoverage": "2018-09-13"
}
}
}
}
we get an error response of the form below:
{
"errors": [
{
"title": "Invalid beginCoverage",
"detail": "Begincoverage must be blank",
"source": {}
},
{
"title": "Invalid endCoverage",
"detail": "Endcoverage must be blank",
"source": {}
}
],
"jsonapi": {
"version": "1.0"
}
}
I was also trying to update "visibilityData" -> "isHidden" and "allowKbToAddTitles" --> Feel that the above error message is misleading not letting us know why "customCoverage" cannot be set. Instead, per Khalilah Gambrell: we could give an error response of this type: [Package not selected. Cannot update.]