@minka/ledger-sdk - npm Package Compare versions

Comparing version 2.8.0 to 2.9.0

package.json

 {
   "name": "@minka/ledger-sdk",
-  "version": "2.8.0",
+  "version": "2.9.0",
   "description": "SDK for Minka Ledger",
@@ -5,0 +5,0 @@ "main": "src/index.js",

types/src/lib/records/ledger-bridge.d.ts

@@ -72,4 +72,43 @@ import { LedgerAccess } from '../common/ledger-access';
     server?: string;
+    /**
+     * Determines how bridge calls for debit claims are grouped in case multiple claims of
+     * one intent are addressed to the same bridge.
+     *
+     * If not defined, claims are not grouped
+     */
+    'debits.claims.groupBy'?: BridgeClaimGrouping;
+    /**
+     * Determines how bridge calls for credit claims are grouped in case multiple claims of
+     * one intent are addressed to the same bridge.
+     *
+     * If not defined, claims are not grouped
+     */
+    'credits.claims.groupBy'?: BridgeClaimGrouping;
 };
 /**
+ * Determines how bridge calls for claims are grouped in case multiple claims of
+ * one intent are addressed to the same bridge.
+ */
+export declare enum BridgeClaimGrouping {
+    /**
+     * With this option, claims will be grouped by exact address of `target.handle` of the claims.
+     *
+     * If there are multiple claims with the same target address,
+     * they will be grouped into single credit entry sent to a target bridge.
+     */
+    address = "address",
+    /**
+     * With this option, claims will be grouped by the actual wallet resolved as target of the address
+     * from `target.handle`
+     *
+     * If there are multiple claims with different `target.handle`,
+     * but they get resolved to the same target wallet (e.g. because of wallet parent hierarchy),
+     * these claims will be grouped together.
+     *
+     * Of course, if the `target.handle` is the same, then the claims will also be grouped together,
+     * just like they would have with the `address` grouping setting.
+     */
+    wallet = "wallet"
+}
+/**
  * Features of a bridge.
@@ -76,0 +115,0 @@ */

types/src/lib/records/ledger-bridge.js

 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.BridgeTraits = exports.LegacyBridgeTrait = exports.BridgeTrait = void 0;
+exports.BridgeTraits = exports.LegacyBridgeTrait = exports.BridgeTrait = exports.BridgeClaimGrouping = void 0;
 /**
+ * Determines how bridge calls for claims are grouped in case multiple claims of
+ * one intent are addressed to the same bridge.
+ */
+var BridgeClaimGrouping;
+(function (BridgeClaimGrouping) {
+    /**
+     * With this option, claims will be grouped by exact address of `target.handle` of the claims.
+     *
+     * If there are multiple claims with the same target address,
+     * they will be grouped into single credit entry sent to a target bridge.
+     */
+    BridgeClaimGrouping["address"] = "address";
+    /**
+     * With this option, claims will be grouped by the actual wallet resolved as target of the address
+     * from `target.handle`
+     *
+     * If there are multiple claims with different `target.handle`,
+     * but they get resolved to the same target wallet (e.g. because of wallet parent hierarchy),
+     * these claims will be grouped together.
+     *
+     * Of course, if the `target.handle` is the same, then the claims will also be grouped together,
+     * just like they would have with the `address` grouping setting.
+     */
+    BridgeClaimGrouping["wallet"] = "wallet";
+})(BridgeClaimGrouping = exports.BridgeClaimGrouping || (exports.BridgeClaimGrouping = {}));
+/**
  * Features of a bridge.
@@ -6,0 +32,0 @@ */

types/src/lib/records/ledger-schema.d.ts

@@ -68,3 +68,4 @@ import { LedgerAccess } from '../common/ledger-access';
     Policy = "policy",
-    Anchor = "anchor"
+    Anchor = "anchor",
+    AnchorLookup = "anchor-lookup"
 }
@@ -71,0 +72,0 @@ /**

types/src/lib/records/ledger-schema.js

@@ -19,2 +19,3 @@ "use strict";
     SchemaRecord["Anchor"] = "anchor";
+    SchemaRecord["AnchorLookup"] = "anchor-lookup";
 })(SchemaRecord = exports.SchemaRecord || (exports.SchemaRecord = {}));
@@ -21,0 +22,0 @@ /**

No alert changes

Improved metrics

Total package byte prevSize

691471

increased by0.45%

Lines of code

14284

increased by0.47%

No dependency changes