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: CONTRIBUTING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ The following [Rush categories](https://rushjs.io/pages/maintainer/add_to_repo/)
27
27
28
28
> Note that npm v6 has some bugs that mean adding new dependencies etc are not properly picked up. Longer term we should consider moving to yarn or pnpm. However in practice this isn't a serious problem and has been possible to be worked around by issuing `rm ./common/config/rush/npm-shrinkwrap.json` and then `rush update`
29
29
30
-
The fv and e2e tests require a set of docker images of Fabric Peers, Orderers and CAs. To ensure you have the correct images ensure these have been dowloaded and tagged. `rush edge-docker` will do this for you.
30
+
The fv and e2e tests require a set of docker images of Fabric Peers, Orderers and CAs. To ensure you have the correct images ensure these have been dowloaded and tagged. `rush edge-docker` will do this for you.
31
31
32
32
They also need to have the `nodeenv` image present - this is build as part of the `rush rebuild` so please ensure this has been run first. It is advisable to clean up the docker containers and images between test runs to avoid any odd behaviour. Commands to help do this are below.
33
33
@@ -50,8 +50,8 @@ For more specific purposes during development the following are useful:
If you want to get a set of `.tar.gz` files of the node modules to use for local testing this command will put them into the `tarballs` directory
52
52
*`rush rebuild --to fvtests` to run the unit tests for the core modules, but not the docker or jsdoc
53
-
*`rush rebuild --to fabric-contract-api` to build, lint and run just the `fabric-contract-api`
54
-
*`rush logs` will show the location of all the log files
53
+
*`rush rebuild --to fabric-contract-api` to build, lint and run just the `fabric-contract-api`
54
+
*`rush logs` will show the location of all the log files
55
55
56
56
To clean up docker
57
57
@@ -67,10 +67,10 @@ The codebase is maintained in [github](https://github.com/hyperledger/fabric-cha
67
67
68
68
## Code of Conduct Guidelines <aname="conduct"></a>
69
69
70
-
See our [Code of Conduct Guidelines](../blob/master/CODE_OF_CONDUCT.md).
70
+
See our [Code of Conduct Guidelines](../blob/main/CODE_OF_CONDUCT.md).
71
71
72
72
## Maintainers <aname="maintainers"></a>
73
73
74
-
Should you have any questions or concerns, please reach out to one of the project's [Maintainers](../blob/master/MAINTAINERS.md).
74
+
Should you have any questions or concerns, please reach out to one of the project's [Maintainers](../blob/main/MAINTAINERS.md).
75
75
76
76
<arel="license"href="http://creativecommons.org/licenses/by/4.0/"><imgalt="Creative Commons License"style="border-width:0"src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <arel="license"href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.
Also: Please see the [Release Manager section](https://github.com/hyperledger/fabric/blob/master/MAINTAINERS.md)
13
+
Also: Please see the [Release Manager section](https://github.com/hyperledger/fabric/blob/main/MAINTAINERS.md)
14
14
15
15
<arel="license"href="http://creativecommons.org/licenses/by/4.0/"><imgalt="Creative Commons License"style="border-width:0"src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <arel="license"href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.
This is the project to support the writing of Contracts with the node.js runtime.
10
+
This is the project to support the writing of Contracts with the node.js runtime.
11
11
12
12
## Documentation
13
13
@@ -24,9 +24,9 @@ For details on what Nodejs runtime and versions of Hyperledger Fabric can be use
24
24
25
25
## npm Shrinkwrap
26
26
27
-
In line with the advice from [npm on shrinkwrap](https://docs.npmjs.com/files/shrinkwrap.json#description) the modules published do not contain a `npm-shrinkwrap.json` file.
27
+
In line with the advice from [npm on shrinkwrap](https://docs.npmjs.com/files/shrinkwrap.json#description) the modules published do not contain a `npm-shrinkwrap.json` file.
28
28
29
-
It is **STRONGLY** recommended therefore that after testing, and before putting your contract into production a `npm-shrinkwrap.json` file is created. When the chaincode is install it will be via a `npm install --production` command.
29
+
It is **STRONGLY** recommended therefore that after testing, and before putting your contract into production a `npm-shrinkwrap.json` file is created. When the chaincode is install it will be via a `npm install --production` command.
30
30
31
31
## Contributing
32
32
@@ -41,4 +41,4 @@ There is also a [release guide](RELEASING.md) describing the process for publish
41
41
Hyperledger Project source code files are made available under the Apache
42
42
License, Version 2.0 (Apache-2.0), located in the [LICENSE](LICENSE) file.
43
43
Hyperledger Project documentation files are made available under the Creative
44
-
Commons Attribution 4.0 International License (CC-BY-4.0), available at http://creativecommons.org/licenses/by/4.0/.
44
+
Commons Attribution 4.0 International License (CC-BY-4.0), available at http://creativecommons.org/licenses/by/4.0/.
Copy file name to clipboardExpand all lines: apis/fabric-contract-api/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ npm install --save fabric-shim
89
89
```
90
90
91
91
### Usage
92
-
The [chaincode interface](https://hyperledger.github.io/fabric-chaincode-node/master/api/fabric-shim.ChaincodeInterface.html) contains two methods to be implemented:
92
+
The [chaincode interface](https://hyperledger.github.io/fabric-chaincode-node/main/api/fabric-shim.ChaincodeInterface.html) contains two methods to be implemented:
93
93
```javascript
94
94
constshim=require('fabric-shim');
95
95
@@ -124,7 +124,7 @@ shim.start(new Chaincode());
124
124
```
125
125
126
126
### API Reference
127
-
Visit [API Reference](https://hyperledger.github.io/fabric-chaincode-node/master/api/) and click on "Classes" link in the navigation bar on the top to view the list of class APIs.
127
+
Visit [API Reference](https://hyperledger.github.io/fabric-chaincode-node/main/api/) and click on "Classes" link in the navigation bar on the top to view the list of class APIs.
The [chaincode interface](https://hyperledger.github.io/fabric-chaincode-node/master/api/fabric-shim.ChaincodeInterface.html) contains two methods to be implemented:
94
+
The [chaincode interface](https://hyperledger.github.io/fabric-chaincode-node/main/api/fabric-shim.ChaincodeInterface.html) contains two methods to be implemented:
0 commit comments