You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: developer-docs-site/docs/concepts/wallet-adapter-concept.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ The [Adapter Core package](https://github.com/aptos-labs/aptos-wallet-adapter/tr
28
28
- Holds the current wallet state and the installed wallets
29
29
- Emits events on different actions and much more
30
30
31
-
Dapps should not *know* this package as dapps interact with the provider, which in turn interacts with the core package; some Types are exposed from the core package for the dapp to use.
31
+
Dapps should not _know_ this package as dapps interact with the provider, which in turn interacts with the core package; some Types are exposed from the core package for the dapp to use.
32
32
33
33
Wallets should implement their own plugin class that extends the basic plugin class (properties + events) interface that lives in the core package.
34
34
@@ -56,20 +56,20 @@ When we started building a wallet adapter, we wanted a structure that can be eas
56
56
57
57
We did research on the existing adapters, got some feedback from our community, and designed this structure to help wallets and dapps in development and when going to production. This structure offers the following benefits:
58
58
59
-
* Modularity (separation of concerns) - separating the adapter into three components can help having more freedom in design, implementation, deployment and usage.
60
-
* Wallets create and own their plugin implementation (instead of having all in the same monorepo):
61
-
- Reduces the packages bundle size used by dapps.
62
-
- Lets them be self-service and support themselves without too much friction.
63
-
- Prevents build failures in case of any bugs/bad implementation/wrong config files/etc.
64
-
* Simplicity - keeps the Provider package very light and small as the major logic is implemented in the core package.
65
-
* Flexibility - for wallets in creating and implementing custom functions.
59
+
- Modularity (separation of concerns) - separating the adapter into three components can help having more freedom in design, implementation, deployment and usage.
60
+
- Wallets create and own their plugin implementation (instead of having all in the same monorepo):
61
+
- Reduces the packages bundle size used by dapps.
62
+
- Lets them be self-service and support themselves without too much friction.
63
+
- Prevents build failures in case of any bugs/bad implementation/wrong config files/etc.
64
+
- Simplicity - keeps the Provider package very light and small as the major logic is implemented in the core package.
65
+
- Flexibility - for wallets in creating and implementing custom functions.
Copy file name to clipboardexpand all lines: developer-docs-site/docs/guides/wallet-adapter-for-dapp.md
+8-7
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ The Aptos Wallet Adapter provides:
24
24
25
25
## Setup
26
26
27
-
Currently, the adapter supports a *React provider* for you to include in your app.
27
+
Currently, the adapter supports a _React provider_ for you to include in your app.
28
28
29
29
Install wallet dependencies you want to include in your app. You can find a list of the wallets in the Aptos Wallet Adapter [README](https://github.com/aptos-labs/aptos-wallet-adapter#supported-wallet-packages).
30
30
@@ -34,13 +34,14 @@ Install the React provider:
34
34
npm install @aptos-labs/wallet-adapter-react
35
35
```
36
36
37
-
Import dependencies:
38
-
TODO: How?
37
+
### Import dependencies:
39
38
40
-
On the App.jsx file, Import the installed wallets:
@@ -52,13 +53,13 @@ import { AptosWalletAdapterProvider } from "@aptos-labs/wallet-adapter-react";
52
53
Wrap your app with the Provider, pass it the plugins (wallets) you want to have on your app as an array, and include an autoConnect option (set to false by default)
0 commit comments