mutation AddKitItemComponent($request: AddKitItemComponentCommandRequestInput!) {
AddKitItemComponent(request: $request) {
componentItemId
quantity
comment
position
}
}{
"request": {
"itemId": "id",
"componentItemId": "id",
"quantity": "value"
}
}{
"data": {
"AddKitItemComponent": {
"componentItemId": "id",
"quantity": "value",
"comment": "string",
"position": 1
}
}
}AddKitItemComponent
Adds a single component to an item’s kit. Fine-grained alternative to replacing the whole component list, for targeted single-component changes without resending the list. The item has to be a kit already; converting a standard item into a kit is a separate endpoint still to be added (WAWI-91105).
If a request with this mutation’s Idempotency-Key was already completed, the response’s extensions contains an idempotency.{responseName} entry with wasReplayed: true.
AddKitItemComponent(request: AddKitItemComponentCommandRequestInput!): AddKitItemComponentCommandResponse!Arguments
ID of the item that was added as a component. A kit component has no own single-value identifier - its identity is the pair of kit and component item - so this doubles as the component's identifier.
How many units of the component item one unit of the kit consumes.
The comment stored on the component. Always a string, never null - an omitted or explicitly null comment in the request is stored and returned as an empty string.
The effective zero-based position of the component. This is the index the component actually ended up at, which differs from the requested one when the request was out of bounds and got clamped.
mutation AddKitItemComponent($request: AddKitItemComponentCommandRequestInput!) {
AddKitItemComponent(request: $request) {
componentItemId
quantity
comment
position
}
}{
"request": {
"itemId": "id",
"componentItemId": "id",
"quantity": "value"
}
}{
"data": {
"AddKitItemComponent": {
"componentItemId": "id",
"quantity": "value",
"comment": "string",
"position": 1
}
}
}Was this page helpful?