@blackfisk/blackfisk-vue-storefront-sdk 1.0.11 → 1.0.13

package/lib/index.cjs.js

@@ -86,7 +86,6 @@ async function getProductListing(props) {
  * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
  */
 async function proxyInstantsearch(props) {
-    // console.log('sdk props', props)
     const { data } = await client.post('proxyInstantsearch', props);
     return data;
 }
@@ -139,13 +138,238 @@ async function getProductFacets(props) {
     return data;
 }
 
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function getCart(props) {
+    const { data } = await client.post('getCart', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function upsertCartItem(props) {
+    const { data } = await client.post('upsertCartItem', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function clearCart(props) {
+    const { data } = await client.post('clearCart', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function loadShippingMethods(props) {
+    const { data } = await client.post('loadShippingMethods', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function setShippingMethod(props) {
+    const { data } = await client.post('setShippingMethod', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function getStripePaymentIntent(props) {
+    const { data } = await client.post('getStripePaymentIntent', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function getSortableAttributes(props) {
+    const { data } = await client.post('getSortableAttributes', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function createCart(props) {
+    const { data } = await client.post('createCart', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function checkout(props) {
+    const { data } = await client.post('checkout', props);
+    return data;
+}
+
 var methods = /*#__PURE__*/Object.freeze({
   __proto__: null,
   getProductCollection: getProductCollection,
   getProductListing: getProductListing,
   proxyInstantsearch: proxyInstantsearch,
   getCollection: getCollection,
-  getProductFacets: getProductFacets
+  getProductFacets: getProductFacets,
+  getCart: getCart,
+  upsertCartItem: upsertCartItem,
+  clearCart: clearCart,
+  loadShippingMethods: loadShippingMethods,
+  setShippingMethod: setShippingMethod,
+  getStripePaymentIntent: getStripePaymentIntent,
+  getSortableAttributes: getSortableAttributes,
+  createCart: createCart,
+  checkout: checkout
 });
 
 /**

package/lib/index.cjs.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.cjs.js","sources":["../src/client/index.ts","../src/methods/getProductCollection/index.ts","../src/methods/getProductListing/index.ts","../src/methods/proxyInstantsearch/index.ts","../src/methods/getCollection/index.ts","../src/methods/getProductFacets/index.ts","../src/connector.ts","../src/index.ts"],"sourcesContent":["import axios from 'axios';\n\nexport const client = axios.create();","import { client } from '../../client';\nimport { getProductCollectionParams, getProductCollectionResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductCollection'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductCollection\n * * Blackfisk endpoint: /v2/vsf/productCollection\n * * Any authenticated client can make this call. A collectionId must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * \n * Optional -\n * * debug: boolean\n * * templateParams: object with the keys required to populate the template chain for the specified collection.\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductCollection({ collectionId: 145, debug: true })\n */\nexport async function getProductCollection(props: getProductCollectionParams) {\n  const { data } = await client.post<getProductCollectionResponse>('getProductCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { getProductListingParams, getProductListingResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductListing'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductListing\n * * Blackfisk endpoint: /v2/vsf/product/variations\n * * Any authenticated client can make this call. A collectionId and either (a familyId, channelListingId, or both) must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * * [familyId || channelListingId]\n * \n * Optional -\n * * debug: boolean\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductListing({ collectionId: 98, familyId: 12345, debug: true })\n */\nexport async function getProductListing(props: getProductListingParams) {\n  const { data } = await client.post<getProductListingResponse>('getProductListing', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function proxyInstantsearch(props: TODO) {\n  // console.log('sdk props', props)\n  const { data } = await client.post<TODO>('proxyInstantsearch', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getCollection(props: TODO) {\n  const { data } = await client.post<TODO>('getCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * API middleware endpoint: /getProductFacets\n * * Blackfisk endpoint: /v2/vsf/product/facets\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getProductFacets(props: TODO) {\n  const { data } = await client.post<TODO>('getProductFacets', props);\n  return data\n}\n","import { client } from './client';\nimport { Options } from './types';\nimport * as methods from './methods/index';\n\n/**\n * Connector methods.\n */\ntype Methods = typeof methods;\n\n/**\n * Initialize the Blackfisk connector.\n */\nexport const blackfiskConnector = (options: Options): Methods => {\n  client.defaults.baseURL = options.apiUrl;\n\n  return methods;\n};\n","import { blackfiskConnector } from './connector';\nimport type { Options } from './types';\nimport type { Module } from '@vue-storefront/sdk';\n\n/**\n * Blackfisk module type.\n */\nexport interface BlackfiskModuleType extends Module {\n  /**\n   * The connector of the Blackfisk module.\n   */\n  connector: ReturnType<typeof blackfiskConnector>;\n}\n\n/**\n * Blackfisk module.\n */\nexport const blackfiskModule = (options: Options): BlackfiskModuleType => {\n  return {\n    connector: blackfiskConnector({\n      apiUrl: options.apiUrl,\n    }),\n    utils: {},\n    subscribers: {},\n  }\n};\n\nexport { client } from './client';\n\nexport * from './types';\n"],"names":["axios"],"mappings":";;;;;;;;;;MAEa,MAAM,GAAGA,yBAAK,CAAC,MAAM;;ACClC;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,oBAAoB,CAAC,KAAiC,EAAA;AAC1E,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA+B,sBAAsB,EAAE,KAAK,CAAC,CAAC;AAChG,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,iBAAiB,CAAC,KAA8B,EAAA;AACpE,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA4B,mBAAmB,EAAE,KAAK,CAAC,CAAC;AAC1F,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,kBAAkB,CAAC,KAAW,EAAA;;AAElD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,oBAAoB,EAAE,KAAK,CAAC,CAAC;AACtE,IAAA,OAAO,IAAI,CAAA;AACb;;ACvBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,aAAa,CAAC,KAAW,EAAA;AAC7C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,eAAe,EAAE,KAAK,CAAC,CAAC;AACjE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,gBAAgB,CAAC,KAAW,EAAA;AAChD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,kBAAkB,EAAE,KAAK,CAAC,CAAC;AACpE,IAAA,OAAO,IAAI,CAAA;AACb;;;;;;;;;;;AChBA;;AAEG;AACI,MAAM,kBAAkB,GAAG,CAAC,OAAgB,KAAa;IAC9D,MAAM,CAAC,QAAQ,CAAC,OAAO,GAAG,OAAO,CAAC,MAAM,CAAC;AAEzC,IAAA,OAAO,OAAO,CAAC;AACjB,CAAC;;ACFD;;AAEG;AACU,MAAA,eAAe,GAAG,CAAC,OAAgB,KAAyB;IACvE,OAAO;QACL,SAAS,EAAE,kBAAkB,CAAC;YAC5B,MAAM,EAAE,OAAO,CAAC,MAAM;SACvB,CAAC;AACF,QAAA,KAAK,EAAE,EAAE;AACT,QAAA,WAAW,EAAE,EAAE;KAChB,CAAA;AACH;;;;;"}
+{"version":3,"file":"index.cjs.js","sources":["../src/client/index.ts","../src/methods/getProductCollection/index.ts","../src/methods/getProductListing/index.ts","../src/methods/proxyInstantsearch/index.ts","../src/methods/getCollection/index.ts","../src/methods/getProductFacets/index.ts","../src/methods/getCart/index.ts","../src/methods/upsertCartItem/index.ts","../src/methods/clearCart/index.ts","../src/methods/loadShippingMethods/index.ts","../src/methods/setShippingMethod/index.ts","../src/methods/getStripePaymentIntent/index.ts","../src/methods/getSortableAttributes/index.ts","../src/methods/createCart/index.ts","../src/methods/checkout/index.ts","../src/connector.ts","../src/index.ts"],"sourcesContent":["import axios from 'axios';\n\nexport const client = axios.create();","import { client } from '../../client';\nimport { getProductCollectionParams, getProductCollectionResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductCollection'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductCollection\n * * Blackfisk endpoint: /v2/vsf/productCollection\n * * Any authenticated client can make this call. A collectionId must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * \n * Optional -\n * * debug: boolean\n * * templateParams: object with the keys required to populate the template chain for the specified collection.\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductCollection({ collectionId: 145, debug: true })\n */\nexport async function getProductCollection(props: getProductCollectionParams) {\n  const { data } = await client.post<getProductCollectionResponse>('getProductCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { getProductListingParams, getProductListingResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductListing'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductListing\n * * Blackfisk endpoint: /v2/vsf/product/variations\n * * Any authenticated client can make this call. A collectionId and either (a familyId, channelListingId, or both) must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * * [familyId || channelListingId]\n * \n * Optional -\n * * debug: boolean\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductListing({ collectionId: 98, familyId: 12345, debug: true })\n */\nexport async function getProductListing(props: getProductListingParams) {\n  const { data } = await client.post<getProductListingResponse>('getProductListing', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function proxyInstantsearch(props: TODO) {\n  const { data } = await client.post<TODO>('proxyInstantsearch', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getCollection(props: TODO) {\n  const { data } = await client.post<TODO>('getCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * API middleware endpoint: /getProductFacets\n * * Blackfisk endpoint: /v2/vsf/product/facets\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getProductFacets(props: TODO) {\n  const { data } = await client.post<TODO>('getProductFacets', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getCart(props: TODO) {\n  const { data } = await client.post<TODO>('getCart', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function upsertCartItem(props: TODO) {\n  const { data } = await client.post<TODO>('upsertCartItem', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function clearCart(props: TODO) {\n  const { data } = await client.post<TODO>('clearCart', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function loadShippingMethods(props: TODO) {\n  const { data } = await client.post<TODO>('loadShippingMethods', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function setShippingMethod(props: TODO) {\n  const { data } = await client.post<TODO>('setShippingMethod', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getStripePaymentIntent(props: TODO) {\n  const { data } = await client.post<TODO>('getStripePaymentIntent', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getSortableAttributes(props: TODO) {\n  const { data } = await client.post<TODO>('getSortableAttributes', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function createCart(props: TODO) {\n  const { data } = await client.post<TODO>('createCart', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function checkout(props: TODO) {\n  const { data } = await client.post<TODO>('checkout', props);\n  return data\n}\n","import { client } from './client';\nimport { Options } from './types';\nimport * as methods from './methods/index';\n\n/**\n * Connector methods.\n */\ntype Methods = typeof methods;\n\n/**\n * Initialize the Blackfisk connector.\n */\nexport const blackfiskConnector = (options: Options): Methods => {\n  client.defaults.baseURL = options.apiUrl;\n\n  return methods;\n};\n","import { blackfiskConnector } from './connector';\nimport type { Options } from './types';\nimport type { Module } from '@vue-storefront/sdk';\n\n/**\n * Blackfisk module type.\n */\nexport interface BlackfiskModuleType extends Module {\n  /**\n   * The connector of the Blackfisk module.\n   */\n  connector: ReturnType<typeof blackfiskConnector>;\n}\n\n/**\n * Blackfisk module.\n */\nexport const blackfiskModule = (options: Options): BlackfiskModuleType => {\n  return {\n    connector: blackfiskConnector({\n      apiUrl: options.apiUrl,\n    }),\n    utils: {},\n    subscribers: {},\n  }\n};\n\nexport { client } from './client';\n\nexport * from './types';\n"],"names":["axios"],"mappings":";;;;;;;;;;MAEa,MAAM,GAAGA,yBAAK,CAAC,MAAM;;ACClC;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,oBAAoB,CAAC,KAAiC,EAAA;AAC1E,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA+B,sBAAsB,EAAE,KAAK,CAAC,CAAC;AAChG,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,iBAAiB,CAAC,KAA8B,EAAA;AACpE,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA4B,mBAAmB,EAAE,KAAK,CAAC,CAAC;AAC1F,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,kBAAkB,CAAC,KAAW,EAAA;AAClD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,oBAAoB,EAAE,KAAK,CAAC,CAAC;AACtE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,aAAa,CAAC,KAAW,EAAA;AAC7C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,eAAe,EAAE,KAAK,CAAC,CAAC;AACjE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,gBAAgB,CAAC,KAAW,EAAA;AAChD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,kBAAkB,EAAE,KAAK,CAAC,CAAC;AACpE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,OAAO,CAAC,KAAW,EAAA;AACvC,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,SAAS,EAAE,KAAK,CAAC,CAAC;AAC3D,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,cAAc,CAAC,KAAW,EAAA;AAC9C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,gBAAgB,EAAE,KAAK,CAAC,CAAC;AAClE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,SAAS,CAAC,KAAW,EAAA;AACzC,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,WAAW,EAAE,KAAK,CAAC,CAAC;AAC7D,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,mBAAmB,CAAC,KAAW,EAAA;AACnD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,qBAAqB,EAAE,KAAK,CAAC,CAAC;AACvE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,iBAAiB,CAAC,KAAW,EAAA;AACjD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,mBAAmB,EAAE,KAAK,CAAC,CAAC;AACrE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,sBAAsB,CAAC,KAAW,EAAA;AACtD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,wBAAwB,EAAE,KAAK,CAAC,CAAC;AAC1E,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,qBAAqB,CAAC,KAAW,EAAA;AACrD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,uBAAuB,EAAE,KAAK,CAAC,CAAC;AACzE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,UAAU,CAAC,KAAW,EAAA;AAC1C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,YAAY,EAAE,KAAK,CAAC,CAAC;AAC9D,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,QAAQ,CAAC,KAAW,EAAA;AACxC,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,UAAU,EAAE,KAAK,CAAC,CAAC;AAC5D,IAAA,OAAO,IAAI,CAAA;AACb;;;;;;;;;;;;;;;;;;;;AChBA;;AAEG;AACI,MAAM,kBAAkB,GAAG,CAAC,OAAgB,KAAa;IAC9D,MAAM,CAAC,QAAQ,CAAC,OAAO,GAAG,OAAO,CAAC,MAAM,CAAC;AAEzC,IAAA,OAAO,OAAO,CAAC;AACjB,CAAC;;ACFD;;AAEG;AACU,MAAA,eAAe,GAAG,CAAC,OAAgB,KAAyB;IACvE,OAAO;QACL,SAAS,EAAE,kBAAkB,CAAC;YAC5B,MAAM,EAAE,OAAO,CAAC,MAAM;SACvB,CAAC;AACF,QAAA,KAAK,EAAE,EAAE;AACT,QAAA,WAAW,EAAE,EAAE;KAChB,CAAA;AACH;;;;;"}

package/lib/index.es.js

@@ -78,7 +78,6 @@ async function getProductListing(props) {
  * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
  */
 async function proxyInstantsearch(props) {
-    // console.log('sdk props', props)
     const { data } = await client.post('proxyInstantsearch', props);
     return data;
 }
@@ -131,13 +130,238 @@ async function getProductFacets(props) {
     return data;
 }
 
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function getCart(props) {
+    const { data } = await client.post('getCart', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function upsertCartItem(props) {
+    const { data } = await client.post('upsertCartItem', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function clearCart(props) {
+    const { data } = await client.post('clearCart', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function loadShippingMethods(props) {
+    const { data } = await client.post('loadShippingMethods', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function setShippingMethod(props) {
+    const { data } = await client.post('setShippingMethod', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function getStripePaymentIntent(props) {
+    const { data } = await client.post('getStripePaymentIntent', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function getSortableAttributes(props) {
+    const { data } = await client.post('getSortableAttributes', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function createCart(props) {
+    const { data } = await client.post('createCart', props);
+    return data;
+}
+
+/**
+ * Method summary - General information about the SDK method, usually a single sentence.
+ *
+ * @remarks
+ * In this section, we have been adding detailed information such as:
+ * * what API middleware endpoint this method is calling,
+ * * what SAP OCC API endpoints are being called as a result of using this method,
+ * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),
+ * * simply everything what helps with understanding how it works.
+ *
+ * @param props
+ * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.
+ *
+ * @returns
+ * Human-friendly information what the SDK methods returns.
+ *
+ * @example
+ * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.
+ */
+async function checkout(props) {
+    const { data } = await client.post('checkout', props);
+    return data;
+}
+
 var methods = /*#__PURE__*/Object.freeze({
   __proto__: null,
   getProductCollection: getProductCollection,
   getProductListing: getProductListing,
   proxyInstantsearch: proxyInstantsearch,
   getCollection: getCollection,
-  getProductFacets: getProductFacets
+  getProductFacets: getProductFacets,
+  getCart: getCart,
+  upsertCartItem: upsertCartItem,
+  clearCart: clearCart,
+  loadShippingMethods: loadShippingMethods,
+  setShippingMethod: setShippingMethod,
+  getStripePaymentIntent: getStripePaymentIntent,
+  getSortableAttributes: getSortableAttributes,
+  createCart: createCart,
+  checkout: checkout
 });
 
 /**

package/lib/index.es.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.es.js","sources":["../src/client/index.ts","../src/methods/getProductCollection/index.ts","../src/methods/getProductListing/index.ts","../src/methods/proxyInstantsearch/index.ts","../src/methods/getCollection/index.ts","../src/methods/getProductFacets/index.ts","../src/connector.ts","../src/index.ts"],"sourcesContent":["import axios from 'axios';\n\nexport const client = axios.create();","import { client } from '../../client';\nimport { getProductCollectionParams, getProductCollectionResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductCollection'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductCollection\n * * Blackfisk endpoint: /v2/vsf/productCollection\n * * Any authenticated client can make this call. A collectionId must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * \n * Optional -\n * * debug: boolean\n * * templateParams: object with the keys required to populate the template chain for the specified collection.\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductCollection({ collectionId: 145, debug: true })\n */\nexport async function getProductCollection(props: getProductCollectionParams) {\n  const { data } = await client.post<getProductCollectionResponse>('getProductCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { getProductListingParams, getProductListingResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductListing'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductListing\n * * Blackfisk endpoint: /v2/vsf/product/variations\n * * Any authenticated client can make this call. A collectionId and either (a familyId, channelListingId, or both) must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * * [familyId || channelListingId]\n * \n * Optional -\n * * debug: boolean\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductListing({ collectionId: 98, familyId: 12345, debug: true })\n */\nexport async function getProductListing(props: getProductListingParams) {\n  const { data } = await client.post<getProductListingResponse>('getProductListing', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function proxyInstantsearch(props: TODO) {\n  // console.log('sdk props', props)\n  const { data } = await client.post<TODO>('proxyInstantsearch', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getCollection(props: TODO) {\n  const { data } = await client.post<TODO>('getCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * API middleware endpoint: /getProductFacets\n * * Blackfisk endpoint: /v2/vsf/product/facets\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getProductFacets(props: TODO) {\n  const { data } = await client.post<TODO>('getProductFacets', props);\n  return data\n}\n","import { client } from './client';\nimport { Options } from './types';\nimport * as methods from './methods/index';\n\n/**\n * Connector methods.\n */\ntype Methods = typeof methods;\n\n/**\n * Initialize the Blackfisk connector.\n */\nexport const blackfiskConnector = (options: Options): Methods => {\n  client.defaults.baseURL = options.apiUrl;\n\n  return methods;\n};\n","import { blackfiskConnector } from './connector';\nimport type { Options } from './types';\nimport type { Module } from '@vue-storefront/sdk';\n\n/**\n * Blackfisk module type.\n */\nexport interface BlackfiskModuleType extends Module {\n  /**\n   * The connector of the Blackfisk module.\n   */\n  connector: ReturnType<typeof blackfiskConnector>;\n}\n\n/**\n * Blackfisk module.\n */\nexport const blackfiskModule = (options: Options): BlackfiskModuleType => {\n  return {\n    connector: blackfiskConnector({\n      apiUrl: options.apiUrl,\n    }),\n    utils: {},\n    subscribers: {},\n  }\n};\n\nexport { client } from './client';\n\nexport * from './types';\n"],"names":[],"mappings":";;MAEa,MAAM,GAAG,KAAK,CAAC,MAAM;;ACClC;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,oBAAoB,CAAC,KAAiC,EAAA;AAC1E,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA+B,sBAAsB,EAAE,KAAK,CAAC,CAAC;AAChG,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,iBAAiB,CAAC,KAA8B,EAAA;AACpE,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA4B,mBAAmB,EAAE,KAAK,CAAC,CAAC;AAC1F,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,kBAAkB,CAAC,KAAW,EAAA;;AAElD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,oBAAoB,EAAE,KAAK,CAAC,CAAC;AACtE,IAAA,OAAO,IAAI,CAAA;AACb;;ACvBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,aAAa,CAAC,KAAW,EAAA;AAC7C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,eAAe,EAAE,KAAK,CAAC,CAAC;AACjE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,gBAAgB,CAAC,KAAW,EAAA;AAChD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,kBAAkB,EAAE,KAAK,CAAC,CAAC;AACpE,IAAA,OAAO,IAAI,CAAA;AACb;;;;;;;;;;;AChBA;;AAEG;AACI,MAAM,kBAAkB,GAAG,CAAC,OAAgB,KAAa;IAC9D,MAAM,CAAC,QAAQ,CAAC,OAAO,GAAG,OAAO,CAAC,MAAM,CAAC;AAEzC,IAAA,OAAO,OAAO,CAAC;AACjB,CAAC;;ACFD;;AAEG;AACU,MAAA,eAAe,GAAG,CAAC,OAAgB,KAAyB;IACvE,OAAO;QACL,SAAS,EAAE,kBAAkB,CAAC;YAC5B,MAAM,EAAE,OAAO,CAAC,MAAM;SACvB,CAAC;AACF,QAAA,KAAK,EAAE,EAAE;AACT,QAAA,WAAW,EAAE,EAAE;KAChB,CAAA;AACH;;;;"}
+{"version":3,"file":"index.es.js","sources":["../src/client/index.ts","../src/methods/getProductCollection/index.ts","../src/methods/getProductListing/index.ts","../src/methods/proxyInstantsearch/index.ts","../src/methods/getCollection/index.ts","../src/methods/getProductFacets/index.ts","../src/methods/getCart/index.ts","../src/methods/upsertCartItem/index.ts","../src/methods/clearCart/index.ts","../src/methods/loadShippingMethods/index.ts","../src/methods/setShippingMethod/index.ts","../src/methods/getStripePaymentIntent/index.ts","../src/methods/getSortableAttributes/index.ts","../src/methods/createCart/index.ts","../src/methods/checkout/index.ts","../src/connector.ts","../src/index.ts"],"sourcesContent":["import axios from 'axios';\n\nexport const client = axios.create();","import { client } from '../../client';\nimport { getProductCollectionParams, getProductCollectionResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductCollection'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductCollection\n * * Blackfisk endpoint: /v2/vsf/productCollection\n * * Any authenticated client can make this call. A collectionId must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * \n * Optional -\n * * debug: boolean\n * * templateParams: object with the keys required to populate the template chain for the specified collection.\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductCollection({ collectionId: 145, debug: true })\n */\nexport async function getProductCollection(props: getProductCollectionParams) {\n  const { data } = await client.post<getProductCollectionResponse>('getProductCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { getProductListingParams, getProductListingResponse } from '@blackfisk/blackfisk-vue-storefront-api/src/api/getProductListing'\n\n/**\n * Executes a collection template chain against Elasticsearch - returning a collection of products.\n * \n * @remarks\n * * API middleware endpoint: /getProductListing\n * * Blackfisk endpoint: /v2/vsf/product/variations\n * * Any authenticated client can make this call. A collectionId and either (a familyId, channelListingId, or both) must be provided.\n * \n * @param props\n * \n * Required\n * * collectionId \n * * [familyId || channelListingId]\n * \n * Optional -\n * * debug: boolean\n * \n * @returns\n * An array of SearchProduct objects.\n * \n * @example\n * const { data: ProductCollection } = await getProductListing({ collectionId: 98, familyId: 12345, debug: true })\n */\nexport async function getProductListing(props: getProductListingParams) {\n  const { data } = await client.post<getProductListingResponse>('getProductListing', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function proxyInstantsearch(props: TODO) {\n  const { data } = await client.post<TODO>('proxyInstantsearch', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getCollection(props: TODO) {\n  const { data } = await client.post<TODO>('getCollection', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * API middleware endpoint: /getProductFacets\n * * Blackfisk endpoint: /v2/vsf/product/facets\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getProductFacets(props: TODO) {\n  const { data } = await client.post<TODO>('getProductFacets', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getCart(props: TODO) {\n  const { data } = await client.post<TODO>('getCart', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function upsertCartItem(props: TODO) {\n  const { data } = await client.post<TODO>('upsertCartItem', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function clearCart(props: TODO) {\n  const { data } = await client.post<TODO>('clearCart', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function loadShippingMethods(props: TODO) {\n  const { data } = await client.post<TODO>('loadShippingMethods', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function setShippingMethod(props: TODO) {\n  const { data } = await client.post<TODO>('setShippingMethod', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getStripePaymentIntent(props: TODO) {\n  const { data } = await client.post<TODO>('getStripePaymentIntent', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function getSortableAttributes(props: TODO) {\n  const { data } = await client.post<TODO>('getSortableAttributes', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function createCart(props: TODO) {\n  const { data } = await client.post<TODO>('createCart', props);\n  return data\n}\n","import { client } from '../../client';\nimport { TODO } from '../../types';\n\n/**\n * Method summary - General information about the SDK method, usually a single sentence.\n * \n * @remarks\n * In this section, we have been adding detailed information such as:\n * * what API middleware endpoint this method is calling,\n * * what SAP OCC API endpoints are being called as a result of using this method,\n * * when this method can be used and when it can’t (e.g. logged-in vs anonymous users),\n * * simply everything what helps with understanding how it works.\n * \n * @param props\n * Just like our API methods, our SDK connector methods accept a single props parameter which carries relevant sub-properties. Therefore, there isn’t much to be described within that TSDoc section.\n * \n * @returns\n * Human-friendly information what the SDK methods returns.\n * \n * @example\n * A short code snippet showing how to use the method. Usually we have more than one @example. We should strive for adding as many examples as possible here, with multiple param configurations.\n */\nexport async function checkout(props: TODO) {\n  const { data } = await client.post<TODO>('checkout', props);\n  return data\n}\n","import { client } from './client';\nimport { Options } from './types';\nimport * as methods from './methods/index';\n\n/**\n * Connector methods.\n */\ntype Methods = typeof methods;\n\n/**\n * Initialize the Blackfisk connector.\n */\nexport const blackfiskConnector = (options: Options): Methods => {\n  client.defaults.baseURL = options.apiUrl;\n\n  return methods;\n};\n","import { blackfiskConnector } from './connector';\nimport type { Options } from './types';\nimport type { Module } from '@vue-storefront/sdk';\n\n/**\n * Blackfisk module type.\n */\nexport interface BlackfiskModuleType extends Module {\n  /**\n   * The connector of the Blackfisk module.\n   */\n  connector: ReturnType<typeof blackfiskConnector>;\n}\n\n/**\n * Blackfisk module.\n */\nexport const blackfiskModule = (options: Options): BlackfiskModuleType => {\n  return {\n    connector: blackfiskConnector({\n      apiUrl: options.apiUrl,\n    }),\n    utils: {},\n    subscribers: {},\n  }\n};\n\nexport { client } from './client';\n\nexport * from './types';\n"],"names":[],"mappings":";;MAEa,MAAM,GAAG,KAAK,CAAC,MAAM;;ACClC;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,oBAAoB,CAAC,KAAiC,EAAA;AAC1E,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA+B,sBAAsB,EAAE,KAAK,CAAC,CAAC;AAChG,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;;;;;AAsBG;AACI,eAAe,iBAAiB,CAAC,KAA8B,EAAA;AACpE,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAA4B,mBAAmB,EAAE,KAAK,CAAC,CAAC;AAC1F,IAAA,OAAO,IAAI,CAAA;AACb;;AC1BA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,kBAAkB,CAAC,KAAW,EAAA;AAClD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,oBAAoB,EAAE,KAAK,CAAC,CAAC;AACtE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,aAAa,CAAC,KAAW,EAAA;AAC7C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,eAAe,EAAE,KAAK,CAAC,CAAC;AACjE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,gBAAgB,CAAC,KAAW,EAAA;AAChD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,kBAAkB,EAAE,KAAK,CAAC,CAAC;AACpE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,OAAO,CAAC,KAAW,EAAA;AACvC,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,SAAS,EAAE,KAAK,CAAC,CAAC;AAC3D,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,cAAc,CAAC,KAAW,EAAA;AAC9C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,gBAAgB,EAAE,KAAK,CAAC,CAAC;AAClE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,SAAS,CAAC,KAAW,EAAA;AACzC,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,WAAW,EAAE,KAAK,CAAC,CAAC;AAC7D,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,mBAAmB,CAAC,KAAW,EAAA;AACnD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,qBAAqB,EAAE,KAAK,CAAC,CAAC;AACvE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,iBAAiB,CAAC,KAAW,EAAA;AACjD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,mBAAmB,EAAE,KAAK,CAAC,CAAC;AACrE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,sBAAsB,CAAC,KAAW,EAAA;AACtD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,wBAAwB,EAAE,KAAK,CAAC,CAAC;AAC1E,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,qBAAqB,CAAC,KAAW,EAAA;AACrD,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,uBAAuB,EAAE,KAAK,CAAC,CAAC;AACzE,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,UAAU,CAAC,KAAW,EAAA;AAC1C,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,YAAY,EAAE,KAAK,CAAC,CAAC;AAC9D,IAAA,OAAO,IAAI,CAAA;AACb;;ACtBA;;;;;;;;;;;;;;;;;;AAkBG;AACI,eAAe,QAAQ,CAAC,KAAW,EAAA;AACxC,IAAA,MAAM,EAAE,IAAI,EAAE,GAAG,MAAM,MAAM,CAAC,IAAI,CAAO,UAAU,EAAE,KAAK,CAAC,CAAC;AAC5D,IAAA,OAAO,IAAI,CAAA;AACb;;;;;;;;;;;;;;;;;;;;AChBA;;AAEG;AACI,MAAM,kBAAkB,GAAG,CAAC,OAAgB,KAAa;IAC9D,MAAM,CAAC,QAAQ,CAAC,OAAO,GAAG,OAAO,CAAC,MAAM,CAAC;AAEzC,IAAA,OAAO,OAAO,CAAC;AACjB,CAAC;;ACFD;;AAEG;AACU,MAAA,eAAe,GAAG,CAAC,OAAgB,KAAyB;IACvE,OAAO;QACL,SAAS,EAAE,kBAAkB,CAAC;YAC5B,MAAM,EAAE,OAAO,CAAC,MAAM;SACvB,CAAC;AACF,QAAA,KAAK,EAAE,EAAE;AACT,QAAA,WAAW,EAAE,EAAE;KAChB,CAAA;AACH;;;;"}