@temple-digital-group/temple-canton-js 2.1.0-beta.0 → 2.1.1

package/README.md

@@ -14,10 +14,10 @@ Call `initialize()` before using any SDK functions. It sets up the config and op
 
 ### Wallet Adapter
 
-For apps using a supported wallet, pass the wallet instance as `WALLET_ADAPTER` or wrap it with the matching adapter factory.
+For apps using a supported wallet, just pass the wallet instance as `WALLET_ADAPTER` (or to `setWalletAdapter`). The SDK recognizes supported wallets and wraps them automatically with default settings — you don't need to call an adapter factory yourself.
 
-- **Loop:** pass the Loop SDK instance directly, or use `createLoopWalletAdapter(loop)`.
-- **Console:** pass the Console wallet instance directly, or use `createConsoleWalletAdapter(consoleWallet)`. The adapter uses `getPrimaryAccount()` and `getContracts()` for reads, and submits the same Temple Daml command object that Loop receives through Console's `prepareExecuteAndWait()` or `prepareExecute()` methods when available.
+- **Loop:** pass the Loop SDK instance directly. Works both in the browser and server-side (Node) — Loop signs locally on the server or delegates to the Loop Wallet UI in the browser.
+- **Console:** **browser only** — pass the Console wallet instance directly. Reads use `getPrimaryAccount()` and `getContracts()`, and commands are submitted through Console's `prepareExecuteAndWait()` (or `prepareExecute()`) — the same Temple Daml command object Loop receives. It can't be used in a server/headless (Node) environment.
 
 ```javascript
 import { initialize } from "@temple-digital-group/temple-canton-js";
@@ -38,6 +38,24 @@ import { setWalletAdapter } from "@temple-digital-group/temple-canton-js";
 setWalletAdapter(wallet);
 ```
 
+#### Adapter Factories (advanced)
+
+You only need the `create*WalletAdapter()` factories when you want to customize how a wallet is wrapped — passing a raw instance (above) already calls them for you with defaults. When you do need custom settings, build the adapter and hand the result to `WALLET_ADAPTER` / `setWalletAdapter`:
+
+- `createLoopWalletAdapter(loop)` — normalize a Loop instance (no extra options).
+- `createConsoleWalletAdapter(consoleWallet, options?)` — normalize a Console instance (browser only) with optional overrides:
+  - `network` — Console network variant (`CANTON_NETWORK`, `CANTON_NETWORK_TEST`, `CANTON_NETWORK_DEV`); defaults from `NETWORK`.
+  - `partyId` — seed a synchronous party id instead of resolving it from `getPrimaryAccount()`.
+  - `parties` — explicit read parties (defaults to the active account party).
+  - `waitForExecution` — `true` (default) submits via `prepareExecuteAndWait()`; `false` uses `prepareExecute()`.
+
+```javascript
+import { setWalletAdapter, createConsoleWalletAdapter } from "@temple-digital-group/temple-canton-js";
+
+// Only needed for custom options — otherwise just pass the raw instance.
+setWalletAdapter(createConsoleWalletAdapter(consoleWallet, { network: "mainnet" }));
+```
+
 | Key              | Required | Description                                       |
 | ---------------- | -------- | ------------------------------------------------- |
 | `API_KEY`        | Yes      | Temple REST API key                               |

package/dist/canton/wallet/console.js

@@ -218,7 +218,12 @@ export function createConsoleWalletAdapter(consoleWallet, options = {}) {
             const useWait = typeof wallet.prepareExecuteAndWait === "function" &&
                 (options.waitForExecution !== false || typeof wallet.prepareExecute !== "function");
             try {
-                return await (useWait ? wallet.prepareExecuteAndWait(prepareRequest) : wallet.prepareExecute(prepareRequest));
+                const result = await (useWait ? wallet.prepareExecuteAndWait(prepareRequest) : wallet.prepareExecute(prepareRequest));
+                // The Console wallet resolves (does not throw) on a successful submit
+                // but often returns nothing — it only rejects on failure/user
+                // rejection. Normalize a void success into a truthy result so callers
+                // don't misread "no return value" as a failure.
+                return result ?? { success: true };
             }
             catch (error) {
                 throw wrapConsoleSubmitError(error);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@temple-digital-group/temple-canton-js",
-  "version": "2.1.0-beta.0",
+  "version": "2.1.1",
   "description": "JavaScript library for interacting with Temple Canton blockchain",
   "type": "module",
   "main": "index.js",

package/src/canton/wallet/console.ts

@@ -268,7 +268,12 @@ export function createConsoleWalletAdapter(consoleWallet: unknown, options: Cons
 				typeof wallet.prepareExecuteAndWait === "function" &&
 				(options.waitForExecution !== false || typeof wallet.prepareExecute !== "function");
 			try {
-				return await (useWait ? wallet.prepareExecuteAndWait!(prepareRequest) : wallet.prepareExecute!(prepareRequest));
+				const result = await (useWait ? wallet.prepareExecuteAndWait!(prepareRequest) : wallet.prepareExecute!(prepareRequest));
+				// The Console wallet resolves (does not throw) on a successful submit
+				// but often returns nothing — it only rejects on failure/user
+				// rejection. Normalize a void success into a truthy result so callers
+				// don't misread "no return value" as a failure.
+				return result ?? { success: true };
 			} catch (error) {
 				throw wrapConsoleSubmitError(error);
 			}