@pollar/react 0.11.3 → 0.11.4-rc.1
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/LICENSE +202 -0
- package/NOTICE +4 -0
- package/README.md +68 -25
- package/dist/index.css +1375 -217
- package/dist/index.css.map +1 -1
- package/dist/index.d.mts +163 -33
- package/dist/index.d.ts +163 -33
- package/dist/index.js +2081 -570
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +2079 -572
- package/dist/index.mjs.map +1 -1
- package/package.json +7 -6
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/NOTICE
ADDED
package/README.md
CHANGED
|
@@ -3,7 +3,36 @@
|
|
|
3
3
|
React bindings for [Pollar](https://pollar.xyz) — drop-in authentication UI, transaction modals, and hooks for
|
|
4
4
|
Stellar and Solana applications.
|
|
5
5
|
|
|
6
|
-
> **0.11.
|
|
6
|
+
> **0.11.4** (candidate `0.11.4-rc.1` on the `next` tag, which requires `@pollar/core@^0.11.4-rc.1`).
|
|
7
|
+
> **KYC by ramp corridor**: `<RampWidget>` lists routes locked by a requirement step and opens that
|
|
8
|
+
> step - `<KycModal>`, `<RequirementFormModal>`, `<RegistryCheckModal>` or `<ProviderRegistrationModal>`
|
|
9
|
+
> (all exported) - then quotes again; `openKycModal()` without a corridor walks the app's own KYC
|
|
10
|
+
> steps. **Redesign**: Send, Swap, Receive, Sessions and Wallet balance follow the new design, keeping the
|
|
11
|
+
> network picker (a multichain app) and Swap's custom buy token. A template you
|
|
12
|
+
> mount yourself gains required handlers (`onMax`, `onPaste`, `onReverse`, `revokeError`,
|
|
13
|
+
> `kycRequired`, `onVerifyRoute`) - see [UPGRADE.md](../../UPGRADE.md). Licensed under Apache-2.0
|
|
14
|
+
> from this release.
|
|
15
|
+
>
|
|
16
|
+
> **Wallet provisioning** (requires `@pollar/core@^0.11.4`, no breaking change). The platform now creates an
|
|
17
|
+
> end-user's Stellar account **in the background**, so a login returns before the account is on
|
|
18
|
+
> the ledger and the first payment in that window is refused by the server. Two things changed
|
|
19
|
+
> here. **A wallet that finishes provisioning now reaches the UI**: `sessionsEqual` did not
|
|
20
|
+
> compare `provisioning` and the context memo's dependency list did not include it, and either
|
|
21
|
+
> one alone froze every screen built on the transition. And the modals say what is happening -
|
|
22
|
+
> **Send** refuses to build a payment while the account is off the ledger and gives the reason
|
|
23
|
+
> (kept apart from the "no transfer path on this network" message, which would otherwise tell
|
|
24
|
+
> someone waiting on a brand-new wallet that Stellar cannot send), **Receive** warns while the
|
|
25
|
+
> address is still unbacked, and the **wallet button** carries the same reason as a banner in its
|
|
26
|
+
> dropdown. `walletNotReadyReason(wallet, chain)` is exported so a custom template phrases the
|
|
27
|
+
> wait the way the built-ins do; `SendModalTemplateProps`, `ReceiveModalTemplateProps` and
|
|
28
|
+
> `WalletButtonTemplateProps` each gain an **optional** `notReadyReason`, so a custom template
|
|
29
|
+
> written before this keeps compiling untouched. In the **ramp widget**: a user whose provider
|
|
30
|
+
> setup is still pending is no longer asked to verify an identity they already verified
|
|
31
|
+
> (`onboardingStatus: 'awaiting_provider'` says the account is being set up and stops the
|
|
32
|
+
> pointless KYC poll), and three failures that printed as raw error codes get sentences.
|
|
33
|
+
> `RampWidgetTemplateProps` gains an optional `onboardingStatus`.
|
|
34
|
+
>
|
|
35
|
+
> Earlier: **0.11.3** required `@pollar/core@^0.11.3`. A **pre-built `PollarClient`
|
|
7
36
|
> passed to `PollarProvider` no longer loses passkey support**: the provider installs the
|
|
8
37
|
> browser passkey ceremony on every path (via core's new `setPasskeyDefaults()`), and an
|
|
9
38
|
> explicit `passkey: undefined` no longer wipes the default. `browserPasskeyCeremony` and
|
|
@@ -162,8 +191,8 @@ const {
|
|
|
162
191
|
// Transactions
|
|
163
192
|
tx, // TransactionState
|
|
164
193
|
buildTx, // (operation, params, options?) => Promise<BuildOutcome>
|
|
165
|
-
signAndSubmitTx, // (unsignedXdr?: string) => Promise<SubmitOutcome> (
|
|
166
|
-
signTx, // (unsignedXdr: string) => Promise<SignOutcome> (external
|
|
194
|
+
signAndSubmitTx, // (unsignedXdr?: string) => Promise<SubmitOutcome> (the smart-wallet path; embedded and external can call it too; XDR optional)
|
|
195
|
+
signTx, // (unsignedXdr: string) => Promise<SignOutcome> (embedded: server signs; external: adapter signs; not for smart wallets)
|
|
167
196
|
sendPayment, // (params: SendPaymentParams) => Promise<SubmitOutcome>
|
|
168
197
|
submitTx, // (signedXdr: string) => Promise<SubmitOutcome>
|
|
169
198
|
buildAndSignAndSubmitTx, // (operation, params, options?) => Promise<SubmitOutcome> (one-shot)
|
|
@@ -211,8 +240,8 @@ const {
|
|
|
211
240
|
network, // StellarNetwork - 'mainnet' | 'testnet'
|
|
212
241
|
setNetwork, // (network: StellarNetwork) => void
|
|
213
242
|
|
|
214
|
-
// KYC
|
|
215
|
-
openKycModal, // (options?: { country?, level?, onApproved? }) => void
|
|
243
|
+
// KYC: without corridorId/providerId it walks the app's own KYC steps
|
|
244
|
+
openKycModal, // (options?: { corridorId?, providerId?, country?, level?, onApproved? }) => void
|
|
216
245
|
|
|
217
246
|
// Ramp (SEP-24 on/off-ramps, wired through core)
|
|
218
247
|
openRampModal, // () => void
|
|
@@ -312,20 +341,23 @@ already wired inside `<PollarProvider>` — and most are exported in case you wa
|
|
|
312
341
|
> (`TxHistoryModalTemplate` / `TransactionModalTemplate`) are public. Mount those instead if you need to drive them
|
|
313
342
|
> yourself.
|
|
314
343
|
|
|
315
|
-
| Component
|
|
316
|
-
|
|
|
317
|
-
| `<WalletButton>`
|
|
318
|
-
| `<SendModal>`
|
|
319
|
-
| `<SwapModal>`
|
|
320
|
-
| `<EarnModal>`
|
|
321
|
-
| `<ReceiveModal>`
|
|
322
|
-
| `<TxHistoryModal>`
|
|
323
|
-
| `<WalletBalanceModal>`
|
|
324
|
-
| `<EnabledAssetsModal>`
|
|
325
|
-
| `<DistributionRulesModal>`
|
|
326
|
-
| `<SessionsModal>`
|
|
327
|
-
| `<KycModal>`
|
|
328
|
-
| `<RampWidget>`
|
|
344
|
+
| Component | Purpose |
|
|
345
|
+
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
346
|
+
| `<WalletButton>` | Drop-in button. Opens login when signed out; signed in, shows the wallet address with a dropdown (Send, Receive, copy address, balance, history, ramp, KYC, distribution rules, sessions, sign out, plus a "Create account" action when the external wallet has no on-chain account yet). Inline arc spinner during in-progress transactions |
|
|
347
|
+
| `<SendModal>` | Full send flow: network picker (shown when the app has more than one chain), asset picker, amount with Max (from the available balance), destination with Paste, inline build > sign > success/error. Sending is available on Stellar and Solana; Polygon can be browsed but not sent from |
|
|
348
|
+
| `<SwapModal>` | On-chain asset-to-asset swap: pick from/to assets and amount, quote across venues, execute (auto-trustline on the buy asset when needed); paste a custom buy token (code + issuer) |
|
|
349
|
+
| `<EarnModal>` | Deposit/withdraw across DeFindex vaults and Blend pools: provider + opportunity selection with live APY, wallet balance, over-spend guards, and auto-trustline on deposit |
|
|
350
|
+
| `<ReceiveModal>` | Wallet address as QR code with copy-to-clipboard (no external QR dependency required) |
|
|
351
|
+
| `<TxHistoryModal>` | Paginated multichain transaction history with auto-fetch on open. A `<ChainSelect>` in the header filters server-side (switching networks refetches and resets to page 1); rows link to their own chain's explorer (stellar.expert for Stellar, explorer.solana.com for Solana) and show the unified `{ amount, unit }` fee |
|
|
352
|
+
| `<WalletBalanceModal>` | Multichain wallet balances (Stellar, Polygon, Solana). A `<ChainSelect>` picks the network and the rows are filtered to it; shows that chain's address plus a refresh button, and each row's issuer with a copy action. An unreadable chain's balance renders as a dash, never as `0`. On Solana testnet each row offers a faucet hint — a devnet SOL faucet on the native row, Circle's USDC faucet on the USDC row |
|
|
353
|
+
| `<EnabledAssetsModal>` | The application's dashboard-enabled assets for the network picked in the header, with per-asset trustline state; establish/remove trustlines (Stellar only - other chains are informational) |
|
|
354
|
+
| `<DistributionRulesModal>` | Manage the wallet's distribution rules |
|
|
355
|
+
| `<SessionsModal>` | Lists every active refresh-token family for the current user with device metadata, marks the local session, per-row revoke, and a "Sign out everywhere" button |
|
|
356
|
+
| `<KycModal>` | Identity verification: hosted (iframe or redirect) flow per option, corridor-scoped when a ramp route asks for it (`corridorId`), or started on one option (`providerId`). Shows review, expiry and retry states; without either id it walks the app's own KYC steps |
|
|
357
|
+
| `<RampWidget>` | Buy/sell crypto via SEP-24 - direction tabs, route comparison, payment instructions (wired to `client.createOnRamp` / `client.createOffRamp`). A route whose corridor has a pending requirement step is listed locked, and the widget opens that step's modal (below) and re-quotes once it is done |
|
|
358
|
+
| `<RequirementFormModal>` | One `FORM` requirement step of a ramp route: renders the form the backend names (`formId`), prefilled with the user's previous answers, and stores the answers encrypted. `<RampWidget>` opens it itself; exported for consumers who build their own route list from `requirementsRequired` |
|
|
359
|
+
| `<RegistryCheckModal>` | One `REGISTRY_CHECK` step (SEGIP through Stereum, `optionId`): the verified identity prefilled and read-only except the surname split and the CI complement; a check the registry did not confirm shows the review state with nothing to retry |
|
|
360
|
+
| `<ProviderRegistrationModal>` | One `PROVIDER_REGISTRATION` step (`corridorId`): lists what the ramp provider receives and registers the user with it on consent; an already registered user is passed through |
|
|
329
361
|
|
|
330
362
|
```tsx
|
|
331
363
|
import { WalletButton } from '@pollar/react';
|
|
@@ -340,12 +372,13 @@ export function Header() {
|
|
|
340
372
|
### Template components
|
|
341
373
|
|
|
342
374
|
Almost every modal ships a pure presentational "template" companion — same name with a `Template` suffix. Use these when
|
|
343
|
-
you want to swap the chrome but keep the data wiring from `usePollar()`. (`<EarnModal
|
|
344
|
-
template yet.)
|
|
375
|
+
you want to swap the chrome but keep the data wiring from `usePollar()`. (`<EarnModal>`, `<RequirementFormModal>`,
|
|
376
|
+
`<RegistryCheckModal>` and `<ProviderRegistrationModal>` are the exceptions: they have no template yet.)
|
|
345
377
|
|
|
346
|
-
> The
|
|
347
|
-
> `
|
|
348
|
-
>
|
|
378
|
+
> The enabled-assets template requires `chains`, `selectedChain` and `onSelectChain`; the wallet-balance, send and
|
|
379
|
+
> receive templates require `selectedChain` and take `chains` / `onSelectChain` as optional - pass both to show the
|
|
380
|
+
> picker, which renders only with two or more chains. Get `chains` (in the app's configured order) from `useChains()`, keep
|
|
381
|
+
> `selectedChain` in your own state, and render `<ChainSelect>` for the stock picker. `useChains()` is preferred over `chainsOf(wallets)` on its
|
|
349
382
|
> own, which cannot know the configured order; if you do call `chainsOf` directly, pass the order as its second
|
|
350
383
|
> argument. `addressForChain(wallets, selectedChain)` gives the address for the picked chain.
|
|
351
384
|
|
|
@@ -370,6 +403,16 @@ template yet.)
|
|
|
370
403
|
|
|
371
404
|
> `onWalletConnect` is **optional** on `<LoginModalTemplate>` (defaults to a no-op).
|
|
372
405
|
|
|
406
|
+
> `notReadyReason` is **optional** on `<SendModalTemplate>`, `<ReceiveModalTemplate>` and
|
|
407
|
+
> `<WalletButtonTemplate>`, and `onboardingStatus` is optional on `<RampWidgetTemplate>` - a custom
|
|
408
|
+
> template written before 0.11.4 keeps compiling and keeps its old wording. Render `notReadyReason`
|
|
409
|
+
> when it is present: it is the sentence for a Stellar account the platform is still creating, and
|
|
410
|
+
> without it a custom Send lets the user build a payment the server will refuse
|
|
411
|
+
> (`SDK_WALLET_NOT_READY`). To phrase it yourself, call the exported
|
|
412
|
+
> `walletNotReadyReason(wallet, chain)`. It gates on `STELLAR` and on the ACCOUNT only, so a
|
|
413
|
+
> Solana wallet, an external wallet (which never carries `provisioning`) and a missing trustline
|
|
414
|
+
> all read as `null` - no reason to block.
|
|
415
|
+
|
|
373
416
|
---
|
|
374
417
|
|
|
375
418
|
### Custom adapters
|
|
@@ -498,4 +541,4 @@ The state types (`TransactionState`, `TxHistoryState`, `WalletBalanceState`, `Ne
|
|
|
498
541
|
|
|
499
542
|
## License
|
|
500
543
|
|
|
501
|
-
|
|
544
|
+
Apache-2.0. See [LICENSE](./LICENSE) and [NOTICE](./NOTICE).
|