@tuwaio/pulsar-core 0.8.0 → 0.8.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -77,7 +77,7 @@ pulsarStore.subscribe((state) => {
|
|
|
77
77
|
|
|
78
78
|
`executeTxAction` rejects when the metadata is invalid, the wallet is on another chain and does not switch, `beforeTxProcess` throws (unless `abortOnTxError: false`) or the wallet rejects the transaction; `initialTx.error` holds the normalized error. For standard EVM transactions it resolves only when tracking has finished, so drive the UI from the store instead of awaiting it.
|
|
79
79
|
|
|
80
|
-
The full React setup, with a wallet connector, typed transactions and the Solana variant, is
|
|
80
|
+
The full React setup, with a wallet connector, typed transactions and the Solana variant, is in the **[React transaction tracking guide](https://docs.tuwa.io/guides/react-transaction-tracking)**.
|
|
81
81
|
|
|
82
82
|
### Preflight checks
|
|
83
83
|
|
|
@@ -115,7 +115,7 @@ With `abortOnTxError: false` (globally or per call), a `beforeTxProcess` error i
|
|
|
115
115
|
|
|
116
116
|
### Remote sync and recovery
|
|
117
117
|
|
|
118
|
-
Pass `onRemoteCreate` to send every new transaction to your backend, for example a server action that forwards it to [Quasar](https://
|
|
118
|
+
Pass `onRemoteCreate` to send every new transaction to your backend, for example a server action that forwards it to [Quasar](https://docs.tuwa.io/quasar). Pulsar keeps working when the backend is slow or down:
|
|
119
119
|
|
|
120
120
|
1. `addTxToPool` writes the transaction to the pool (and to `localStorage`) first, with `syncStatus: 'pending-sync'` and its key in `unsyncedTxKeys`, and the tracker starts right away. `onRemoteCreate` runs in the background: when it resolves, the transaction becomes `'synced'` and the key is removed; when it rejects, the error is logged and the key stays. Reject (throw) on failure: a resolved promise counts as synced.
|
|
121
121
|
2. The trackers keep following the transaction in the browser, so its status stays correct without the backend. A slow backend never delays tracking, and a sync interrupted by a closed tab is still listed after the reload.
|
|
@@ -123,7 +123,7 @@ Pass `onRemoteCreate` to send every new transaction to your backend, for example
|
|
|
123
123
|
|
|
124
124
|
`onRemoteCreate` receives a copy of the transaction without `pimlicoApiKey` and `gelatoApiKey`: configure provider keys on the backend instead (for Quasar, in the app settings). `bundlerUrl` is sent, so do not put API keys in it.
|
|
125
125
|
|
|
126
|
-
To show the remote history, `createTxInMemoryStore` merges the pages returned by your `getHistory` with the local pool (terminal transactions are never overwritten by stale data, and transactions that fail validation are skipped), and `injectExternalPendingTxs` adds pending transactions from other devices to the local pool and tracks them. The complete Next.js + Quasar integration, with server actions and SIWX sessions, is in the **[
|
|
126
|
+
To show the remote history, `createTxInMemoryStore` merges the pages returned by your `getHistory` with the local pool (terminal transactions are never overwritten by stale data, and transactions that fail validation are skipped), and `injectExternalPendingTxs` adds pending transactions from other devices to the local pool and tracks them. The complete Next.js + Quasar integration, with server actions and SIWX sessions, is in the **[Quasar transaction sync guide](https://docs.tuwa.io/guides/quasar-transaction-sync)**.
|
|
127
127
|
|
|
128
128
|
---
|
|
129
129
|
|