patchPrefWithHttpInfo method
Save the preference keys your surface owns, leaving every other key alone
Merges a JSON object key-wise into the signed-in caller's OWN preference document and answers with the whole document after the merge, so a surface saves theme without having to send back the density another surface owns. The merge is SHALLOW and the key space is open: an unnamed key is left untouched, a named key is replaced whole, and a key sent with a null value is DELETED. The subject is the <owner>/<name> identity built from the validated credential and is the mandatory predicate on the write, so there is no path to another user's preferences — not for an org admin, not for a platform SuperAdmin. Fails closed: no validated principal is 403; an empty body or a literal null is 400; and a patch or a resulting document over 16 KiB or 128 keys is 413.
Note: This method returns the HTTP Response.
Implementation
Future<Response> patchPrefWithHttpInfo() async {
// ignore: prefer_const_declarations
final path = r'/v1/pref';
// ignore: prefer_final_locals
Object? postBody;
final queryParams = <QueryParam>[];
final headerParams = <String, String>{};
final formParams = <String, String>{};
const contentTypes = <String>[];
return apiClient.invokeAPI(
path,
'PATCH',
queryParams,
postBody,
headerParams,
formParams,
contentTypes.isEmpty ? null : contentTypes.first,
);
}