@gala-chain/launchpad-sdk 3.16.3 → 3.17.0
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/CHANGELOG.md +54 -0
- package/dist/constants/version.generated.d.ts +1 -1
- package/dist/index.cjs.js +1 -1
- package/dist/index.esm.js +1 -1
- package/dist/index.js +1 -1
- package/dist/services/PriceHistoryService.d.ts +1 -1
- package/dist/services/PriceHistoryService.d.ts.map +1 -1
- package/dist/types/priceHistory.dto.d.ts +6 -9
- package/dist/types/priceHistory.dto.d.ts.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,59 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 3.17.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- Simplify price history response structure with tokenId field
|
|
8
|
+
|
|
9
|
+
Replace individual token class fields (collection, category, type, additionalKey) with a single
|
|
10
|
+
pipe-delimited tokenId field in PriceSnapshot responses.
|
|
11
|
+
|
|
12
|
+
Changes:
|
|
13
|
+
- PriceSnapshot interface now has tokenId: string instead of separate fields
|
|
14
|
+
- Both fetchPriceHistory and fetchPrices return simplified snapshots
|
|
15
|
+
- Updated response transformation logic to construct tokenId from API data
|
|
16
|
+
- Made httpClient optional in PriceHistoryService constructor (only required when using
|
|
17
|
+
fetchPriceHistory, not for MySQL-only methods)
|
|
18
|
+
|
|
19
|
+
Example response change:
|
|
20
|
+
- Before: { price: '0.166', ..., collection: 'GALA', category: 'Unit', type: 'none',
|
|
21
|
+
additionalKey: 'none' }
|
|
22
|
+
- After: { price: '0.166', ..., tokenId: 'GALA|Unit|none|none' }
|
|
23
|
+
|
|
24
|
+
## 3.16.4
|
|
25
|
+
|
|
26
|
+
### Patch Changes
|
|
27
|
+
|
|
28
|
+
- ## Fix: Support Both GalaChain Token Format Variants (v3.16.4)
|
|
29
|
+
|
|
30
|
+
Enhanced token format handling to support both GalaChain token ID formats seamlessly.
|
|
31
|
+
|
|
32
|
+
GalaChain supports two token ID format variants:
|
|
33
|
+
|
|
34
|
+
**Format 1: Standard (collection="Token")**
|
|
35
|
+
|
|
36
|
+
```
|
|
37
|
+
Token|Unit|GALA|none → GALA$Unit$none$none
|
|
38
|
+
Token|Unit|SILK|none → SILK$Unit$none$none
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
**Format 2: Direct (collection=token name)**
|
|
42
|
+
|
|
43
|
+
```
|
|
44
|
+
GALA|Unit|none|none → GALA$Unit$none$none
|
|
45
|
+
SILK|Unit|none|none → SILK$Unit$none$none
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
Both are now handled correctly by detecting which field contains the token name and extracting it
|
|
49
|
+
appropriately for the DEX Backend API.
|
|
50
|
+
|
|
51
|
+
Changes:
|
|
52
|
+
- Detect token name location based on collection field
|
|
53
|
+
- Extract from `type` field if collection="Token", otherwise from `collection` field
|
|
54
|
+
- Build API format consistently: `{TOKEN_NAME}$Unit$none$none`
|
|
55
|
+
- Both token format variants now work identically
|
|
56
|
+
|
|
3
57
|
## 3.16.3
|
|
4
58
|
|
|
5
59
|
### Patch Changes
|