We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/allImages
See RFC-019 for more info.
Add PATCH support for /customers/{c}/allImages, accepting payloads in format:
/customers/{c}/allImages
{ "member": [ {"id": "1/2/a"},{"id": "1/2/b"} ], "field": "manifests", "operation": "add|remove|replace", "value": [ "m123" ] }
"members"
"field"
manifests
"operation"
null
[]
"value"
Returning HydraCollection of images. If no images found return an empty HydraCollection.
Writes should be atomic - competing requests that come in at the same time should both be recorded in the database. See npgsql EF support for arrays and RFC-019#implementation-details
Optional:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
See RFC-019 for more info.
Add PATCH support for
/customers/{c}/allImages
, accepting payloads in format:"members"
is the list of image ids to apply PATCH to"field"
specifies which field is being modified -manifests
is the only valid value for now (400 if other field)"operation"
can be one of (400 if other value):null
is rejected with 400 as need to be explicit, use[]
to clear values."value"
is the value(s) to add/remove/replaceReturning HydraCollection of images. If no images found return an empty HydraCollection.
Writes should be atomic - competing requests that come in at the same time should both be recorded in the database. See npgsql EF support for arrays and RFC-019#implementation-details
Optional:
The text was updated successfully, but these errors were encountered: