@soltech/fluid-common 0.8.8 → 0.8.9
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 +11 -0
- package/lib/index.d.ts +1 -0
- package/package.json +1 -1
- package/src/index.ts +1 -0
package/README.md
CHANGED
|
@@ -7,3 +7,14 @@
|
|
|
7
7
|
2. Bump the package version according to change severity
|
|
8
8
|
3. Commit
|
|
9
9
|
4. run `npm run pub` - it'll build the package, publish it to npm and push changes to github
|
|
10
|
+
|
|
11
|
+
But during the time of development, another version could have been deployed, without your change only available in your Pull Request.
|
|
12
|
+
And you need to keep your branch updated with the `main` one.
|
|
13
|
+
In that case, follow these steps:
|
|
14
|
+
|
|
15
|
+
1. make sure your commons is up to date with main
|
|
16
|
+
2. create a branch out of main and make your changes or update the branch of the PR
|
|
17
|
+
3. bump the package version according to severity - that’s a bit tricky as that version may already be taken by a parallel work, so it’s worth checking other active branches or the npm itself
|
|
18
|
+
4. commit and push the branch
|
|
19
|
+
5. run `npm run pub` to publish the package
|
|
20
|
+
6. refer to the package in your branch in another repo
|
package/lib/index.d.ts
CHANGED
|
@@ -48,6 +48,7 @@ export interface WalletConfig {
|
|
|
48
48
|
transactionToggleDisplayed: boolean;
|
|
49
49
|
kycDepositLimit: number | null;
|
|
50
50
|
autofillCreditCardName: boolean;
|
|
51
|
+
contactSupportLink: string;
|
|
51
52
|
}
|
|
52
53
|
export interface WalletConfigParams {
|
|
53
54
|
contentText: Record<string, ContentType>;
|
package/package.json
CHANGED