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: packages/assets-controllers/CHANGELOG.md
+42-1Lines changed: 42 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
6
6
7
7
## [Unreleased]
8
8
9
+
## [15.0.0]
10
+
### Changed
11
+
-**BREAKING**: `NftController` now expects `getNetworkClientById` in constructor options ([#1698](https://github.com/MetaMask/core/pull/1698))
12
+
-**BREAKING**: `NftController.addNft` function signature has changed ([#1698](https://github.com/MetaMask/core/pull/1698))
13
+
- Previously
14
+
```
15
+
address: string,
16
+
tokenId: string,
17
+
nftMetadata?: NftMetadata,
18
+
accountParams?: {
19
+
userAddress: string;
20
+
chainId: Hex;
21
+
},
22
+
source = Source.Custom,
23
+
```
24
+
now:
25
+
```
26
+
tokenAddress: string,
27
+
tokenId: string,
28
+
{
29
+
nftMetadata?: NftMetadata;
30
+
chainId?: Hex; // extracts from AccountParams
31
+
userAddress?: string // extracted from AccountParams
32
+
source?: Source;
33
+
networkClientId?: NetworkClientId; // new
34
+
},
35
+
```
36
+
- `NftController.addNftVerifyOwnership`: Now accepts optional 3rd argument `networkClientId` which is used to fetch NFT metadata and determine by which chainId the added NFT should be stored in state. Also accepts optional 4th argument `source` used for metrics to identify the flow in which the NFT was added to the wallet. ([#1698](https://github.com/MetaMask/core/pull/1698))
37
+
- `NftController.isNftOwner`: Now accepts optional `networkClientId` which is used to instantiate the provider for the correct chain and call the NFT contract to verify ownership ([#1698](https://github.com/MetaMask/core/pull/1698))
38
+
- `NftController.addNft` will use the chainId value derived from `networkClientId` if provided ([#1698](https://github.com/MetaMask/core/pull/1698))
39
+
- `NftController.watchNft` options now accepts optional `networkClientId` which is used to fetch NFT metadata and determine by which chainId the added NFT should be stored in state ([#1698](https://github.com/MetaMask/core/pull/1698))
40
+
- Bump dependency on `@metamask/utils` to ^8.1.0 ([#1639](https://github.com/MetaMask/core/pull/1639))
41
+
- Bump dependency and peer dependency on `@metamask/approval-controller` to ^4.0.0
42
+
- Bump dependency on `@metamask/base-controller` to ^3.2.3
43
+
- Bump dependency on `@metamask/controller-utils` to ^5.0.2
44
+
- Bump dependency and peer dependency on `@metamask/network-controller` to ^14.0.0
45
+
46
+
### Fixed
47
+
- Fix bug in TokensController where batched `addToken` overwrote each other because mutex was acquired after reading state ([#1768](https://github.com/MetaMask/core/pull/1768))
48
+
9
49
## [14.0.0]
10
50
### Changed
11
51
- Update TypeScript to v4.8.x ([#1718](https://github.com/MetaMask/core/pull/1718))
@@ -280,7 +320,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
280
320
### Changed
281
321
- Use Ethers for AssetsContractController ([#845](https://github.com/MetaMask/core/pull/845))
0 commit comments