@nautical-commerce/graphql-schema 4.18.0 → 4.19.0

package/nautical/schema.graphql

@@ -2743,6 +2743,18 @@ type BulkProductVideoError {
   index: Int
 }
 
+"""A warning on a product a bulk mutation created or updated."""
+type BulkProductWarning {
+  """Index of the input row the product came from."""
+  index: Int!
+
+  """Code of the warning message."""
+  code: ProductWarningEnum!
+
+  """Warning message."""
+  message: String!
+}
+
 """Represents errors from bulk stock operations."""
 type BulkStockError {
   field: String
@@ -5258,7 +5270,9 @@ type CustomerEvent implements Node {
   """Number of objects concerned by the event."""
   count: Int
 
-  """User who performed the action."""
+  """
+  User whose activity log holds the event: the customer for self-service events, and the staff user who acted for staff actions. Null when an app with no attached user made the change.
+  """
   user: User
 
   """The concerned order."""
@@ -15714,6 +15728,11 @@ type ProductBulkCreate {
   List of errors that occurred executing the mutation. An entry's `index` identifies the input row it came from. Note that an entry with `field: "image"` does NOT mean the row failed: that product was created and only its rejected image was dropped, so treating every `index` in this list as a failed row would mark a successfully created product as failed.
   """
   bulkProductErrors: [BulkProductError!]!
+
+  """
+  Warnings on the created or updated products, each with the index of the input row its product came from. They are the product's own `warnings`. A product created without variants carries `DEFAULT_VARIANT_REQUIRED` until it gets one, so `hasWarnings` is true for each such product: look for a code instead, such as `PRODUCT_ATTRIBUTE_VALUE_REQUIRED` for a required attribute left without a value. Only a row whose product is in `products` has entries. A row refused only its image keeps its product, and so its warnings. A row whose attributes could not be written has none: its product is saved unpublished, and reported only in `bulkProductErrors`.
+  """
+  bulkProductWarnings: [BulkProductWarning!]!
 }
 
 input ProductBulkCreateInput {
@@ -15827,6 +15846,16 @@ input ProductBulkCreateInput {
   When enabled, other sellers can create their own variants on this product.
   """
   allowSellerVariants: Boolean = null
+
+  """
+  Public metadata for the product. On an upsert the keys are merged into the product's metadata as metadataUpdate merges them: keys not sent are kept. A row whose metadata is refused is skipped; the other rows are still written.
+  """
+  metadata: [MetadataInput!] = null
+
+  """
+  Private metadata for the product, merged on an upsert as privateMetadataUpdate merges it. Needs the permission privateMetadataUpdate needs for a product. A row whose metadata is refused is skipped; the other rows are still written.
+  """
+  privateMetadata: [MetadataInput!] = null
 }
 
 """Result of product bulk delete mutation."""
@@ -16096,6 +16125,7 @@ enum ProductErrorCode {
   COLLECTION_ALLOWED_FOR_VARIANTS_ONLY
   INVENTORY_FIELD_CANNOT_BE_EDITED
   REQUIRED_PRODUCT_ID_OR_PRODUCT_TYPE_ID
+  MEDIA_FETCH_FAILED
 }
 
 """Product fields available for export."""
@@ -17296,14 +17326,16 @@ type ProductVariantAuditEventCountableEdge {
 
 """Result of product variant bulk create mutation."""
 type ProductVariantBulkCreate {
-  """Number of variants created."""
+  """
+  Number of variants created or updated. A row whose externalSource and externalId match a variant of the product updates it.
+  """
   count: Int!
 
-  """The created product variants."""
+  """The created and updated product variants."""
   productVariants: [ProductVariant!]!
 
   """
-  List of errors that occurred executing the mutation. Carries two kinds. If `count` is 0 and `productVariants` is empty the batch was rejected outright and nothing was created. Otherwise the batch committed and any entry with `field: "image"` is advisory: that row's image was rejected and dropped, but the variant at `index` was created.
+  List of errors that occurred executing the mutation. Carries two kinds. If `count` is 0 and `productVariants` is empty the batch was rejected outright and nothing was written. Otherwise the batch committed and every entry is advisory: the variant at `index` was written, but with `field: "image"` its image was rejected, or not added because the row updated an existing variant, and with `field: "stocks"` its stocks were not applied because the row updated an existing variant.
   """
   productErrors: [BulkProductError!]!
 
@@ -17381,6 +17413,16 @@ input ProductVariantBulkCreateInput {
 
   """Initial image to associate with the variant."""
   image: Upload = null
+
+  """
+  Public metadata for the variant. On an upsert the keys are merged into the variant's metadata as metadataUpdate merges them: keys not sent are kept. A row whose metadata is refused fails the whole batch, as any refused row does here.
+  """
+  metadata: [MetadataInput!] = null
+
+  """
+  Private metadata for the variant, merged on an upsert as privateMetadataUpdate merges it. Needs the permission privateMetadataUpdate needs for a variant. A row whose metadata is refused fails the whole batch, as any refused row does here.
+  """
+  privateMetadata: [MetadataInput!] = null
 }
 
 """Result of product variant bulk delete mutation."""
@@ -18059,6 +18101,7 @@ enum ProductWarningEnum {
   SELLER_PAUSED
   SELLER_DIGITAL_SUSPENDED
   SELLER_AGREEMENT_UNACKNOWLEDGED
+  IMAGE_FETCH_FAILED
 }
 
 """Result of products export mutation."""
@@ -23527,6 +23570,11 @@ type TokenRefresh {
   """New JWT token."""
   token: String
 
+  """
+  New JWT refresh token. Every refresh issues one: store it in place of the token sent, so the session lasts from its last use rather than from sign-in, up to a fixed limit after sign-in. Returned when the refresh token was sent as an argument; a refresh from the cookie updates the cookie instead.
+  """
+  refreshToken: String
+
   """The authenticated user."""
   user: User
 
@@ -23737,7 +23785,7 @@ type User implements Node & ObjectWithMetadata {
   events: [CustomerEvent!]!
 
   """
-  Unified change-history feed for this customer. Projects the legacy CustomerEvent log into a TimelineEntry list ordered most-recent-first, so customer history renders through the same dashboard component as the order, seller and product timelines. Note that CustomerEvent records the customer an event concerns, not who performed it, so entries report an unknown actor rather than attributing staff actions to the customer. Optional `kinds` argument filters server-side.
+  Unified change-history feed for this customer. Projects the legacy CustomerEvent log into a TimelineEntry list ordered most-recent-first, so customer history renders through the same dashboard component as the order, seller and product timelines. Entries report an unknown actor, because CustomerEvent.user is the customer an event concerns on some events and the staff user who acted on others. Optional `kinds` argument filters server-side.
   """
   timeline(kinds: [TimelineEntryKind!] = null): [TimelineEntry!]!
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nautical-commerce/graphql-schema",
-  "version": "4.18.0",
+  "version": "4.19.0",
   "description": "Traide API GraphQL Schema",
   "main": "./nautical/schema.graphql",
   "scripts": {