@notabene/javascript-sdk 2.20.0-next.3 → 2.20.0-next.4

package/dist/cjs/notabene.d.ts

@@ -3347,6 +3347,30 @@ export declare interface TransactionOptions {
     contactSupport?: ContactSupportConfig;
     consent?: ConsentConfig;
     autoSubmit?: boolean;
+    /**
+     * Wallet connection behaviour.
+     */
+    wallets?: {
+        /**
+         * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+         *
+         * Prefer a wallet's `https://` universal link over its custom scheme (for example
+         * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+         * in-app webview, which cannot launch another app on its own and so needs the host app
+         * to handle every custom scheme it might encounter.
+         *
+         * Off by default. Has no effect for wallets whose registry entry declares no universal
+         * link, which is most of them today. Where a wallet does declare one, this also changes
+         * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+         * the wallet's Android app links are not verified.
+         *
+         * Behaviour therefore depends on the wallet and on your host app. Verify against the
+         * wallets your users actually use before enabling this in production.
+         *
+         * @defaultValue false
+         */
+        experimentalPreferUniversalLinks?: boolean;
+    };
 }
 
 /**

package/dist/cjs/package.json

@@ -10,7 +10,7 @@
   "author": "Notabene <developers@notabene.id>",
   "license": "MIT",
   "packageManager": "yarn@4.5.1",
-  "version": "2.20.0-next.3",
+  "version": "2.20.0-next.4",
   "source": "src/notabene.ts",
   "main": "dist/cjs/notabene.cjs",
   "module": "dist/esm/notabene.js",

package/dist/esm/notabene.d.ts

@@ -3347,6 +3347,30 @@ export declare interface TransactionOptions {
     contactSupport?: ContactSupportConfig;
     consent?: ConsentConfig;
     autoSubmit?: boolean;
+    /**
+     * Wallet connection behaviour.
+     */
+    wallets?: {
+        /**
+         * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+         *
+         * Prefer a wallet's `https://` universal link over its custom scheme (for example
+         * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+         * in-app webview, which cannot launch another app on its own and so needs the host app
+         * to handle every custom scheme it might encounter.
+         *
+         * Off by default. Has no effect for wallets whose registry entry declares no universal
+         * link, which is most of them today. Where a wallet does declare one, this also changes
+         * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+         * the wallet's Android app links are not verified.
+         *
+         * Behaviour therefore depends on the wallet and on your host app. Verify against the
+         * wallets your users actually use before enabling this in production.
+         *
+         * @defaultValue false
+         */
+        experimentalPreferUniversalLinks?: boolean;
+    };
 }
 
 /**

package/dist/esm/package.json

@@ -10,7 +10,7 @@
   "author": "Notabene <developers@notabene.id>",
   "license": "MIT",
   "packageManager": "yarn@4.5.1",
-  "version": "2.20.0-next.3",
+  "version": "2.20.0-next.4",
   "source": "src/notabene.ts",
   "main": "dist/cjs/notabene.cjs",
   "module": "dist/esm/notabene.js",

package/dist/notabene.d.ts

@@ -3347,6 +3347,30 @@ export declare interface TransactionOptions {
     contactSupport?: ContactSupportConfig;
     consent?: ConsentConfig;
     autoSubmit?: boolean;
+    /**
+     * Wallet connection behaviour.
+     */
+    wallets?: {
+        /**
+         * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+         *
+         * Prefer a wallet's `https://` universal link over its custom scheme (for example
+         * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+         * in-app webview, which cannot launch another app on its own and so needs the host app
+         * to handle every custom scheme it might encounter.
+         *
+         * Off by default. Has no effect for wallets whose registry entry declares no universal
+         * link, which is most of them today. Where a wallet does declare one, this also changes
+         * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+         * the wallet's Android app links are not verified.
+         *
+         * Behaviour therefore depends on the wallet and on your host app. Verify against the
+         * wallets your users actually use before enabling this in production.
+         *
+         * @defaultValue false
+         */
+        experimentalPreferUniversalLinks?: boolean;
+    };
 }
 
 /**

package/package.json

@@ -10,7 +10,7 @@
   "author": "Notabene <developers@notabene.id>",
   "license": "MIT",
   "packageManager": "yarn@4.5.1",
-  "version": "2.20.0-next.3",
+  "version": "2.20.0-next.4",
   "source": "src/notabene.ts",
   "main": "dist/cjs/notabene.cjs",
   "module": "dist/esm/notabene.js",

package/src/types.ts

@@ -1044,6 +1044,30 @@ export interface TransactionOptions {
   contactSupport?: ContactSupportConfig; // Requires 'contact-support' in agentSections
   consent?: ConsentConfig; // Defaults to true
   autoSubmit?: boolean; // Defaults to false
+  /**
+   * Wallet connection behaviour.
+   */
+  wallets?: {
+    /**
+     * EXPERIMENTAL. No stability guarantee; may change or be removed in a minor release.
+     *
+     * Prefer a wallet's `https://` universal link over its custom scheme (for example
+     * `metamask://`) when connecting a mobile wallet. Useful when embedding inside a mobile
+     * in-app webview, which cannot launch another app on its own and so needs the host app
+     * to handle every custom scheme it might encounter.
+     *
+     * Off by default. Has no effect for wallets whose registry entry declares no universal
+     * link, which is most of them today. Where a wallet does declare one, this also changes
+     * behaviour in an ordinary mobile browser, and a universal link can be worse there if
+     * the wallet's Android app links are not verified.
+     *
+     * Behaviour therefore depends on the wallet and on your host app. Verify against the
+     * wallets your users actually use before enabling this in production.
+     *
+     * @defaultValue false
+     */
+    experimentalPreferUniversalLinks?: boolean;
+  };
 }
 /**
  * Component Message Type enum representing different message types that can be sent