createJsonMutation since v0.2
Formulae
createJsonMutation(config)
Config fields:
params?: parameters for the Mutation- You can declare Mutation parameters by call
declareParamsfunction. - If not passed, Mutation will be created without parameters.
- You can declare Mutation parameters by call
request: declarative rules to formulate request to the API.method: Stringurl: Sourced stringbody: Sourced Json, any value which can be serialized to JSON and parsed back without loses by JavaScript native module JSON. For example,{ a: 1, b: 2 }. Note that body cannot be used inGETandHEADrequests.query?: Sourced object, keys of the object must beStringand values must beStringorArray<String>or (since v0.8) Sourced String containing ready-to-use query stringheaders?: Sourced object, keys of the object must beStringand values must beStringorArray<String>credentials?: since v0.7 String, available values:omit— do not include credentialssame-origin— include credentials only if the request URL is the same origininclude— include credentials on all requests
response: declarative rules to handle response from the API.contract: Contract allows you to validate the response and decide how your application should treat it — as a success response or as a failed one.validate?: Validator allows you to dynamically validate received data.mapData?: optional mapper for the response data, available overloads:(res) => mapped{ source: Store, fn: (data, res) => mapped }
resobject contains:result: parsed and validated response dataparams: params which were passed to the Mutationheaders: since v0.13 raw response headers
mapError?: since v0.14 optional mapper for the error, available overloads:(err) => mapped{ source: Store, fn: (err, sourceValue) => mapped }
errobject contains:error: the original error that occurredparams: params which were passed to the Mutationheaders: raw response headers (available for HTTP errors and contract/validation errors where the response was received, not available for network errors)
status.expected:numberorArray<number>of expected HTTP status codes, if the response status code is not in the list, the mutation will be treated as failed
Examples
Error mapping
You can transform errors before they are passed to the Mutation using mapError:
const loginMutation = createJsonMutation({
params: declareParams<{ login: string; password: string }>(),
request: {
method: 'POST',
url: 'https://api.salo.com/login',
body: ({ login, password }) => ({ login, password }),
},
response: {
contract: loginContract,
mapError({ error, params, headers }) {
if (isHttpError({ status: 401, error })) {
return {
type: 'unauthorized',
message: 'Invalid credentials',
requestId: headers?.get('X-Request-Id'),
};
}
if (isHttpError({ status: 429, error })) {
return {
type: 'rate_limited',
message: 'Too many attempts, please try again later',
requestId: headers?.get('X-Request-Id'),
};
}
return {
type: 'unknown',
message: 'Something went wrong',
requestId: headers?.get('X-Request-Id'),
};
},
},
});With a sourced mapper:
const $errorMessages = createStore({
401: 'Invalid credentials',
429: 'Too many attempts',
});
const loginMutation = createJsonMutation({
params: declareParams<{ login: string; password: string }>(),
request: {
method: 'POST',
url: 'https://api.salo.com/login',
body: ({ login, password }) => ({ login, password }),
},
response: {
contract: loginContract,
mapError: {
source: $errorMessages,
fn({ error, headers }, messages) {
if (isHttpError({ error })) {
return {
message: messages[error.status] ?? 'Unknown error',
requestId: headers?.get('X-Request-Id'),
};
}
return { message: 'Network error', requestId: null };
},
},
},
});