Explore VS Code plugin development
Tasks | Expectation |
---|
Compile the VS Code plugin, package it | - Ship the package.
- Install the package on any other machine.
- The plugin should be installed and available after restarts.
|
Create a new Explorer header | - Create a new header under the explorer section.
- Add a button to the new header. Print the button name upon click.
|
Either JavaScript, Java or Go debugger, add actions around it | - Call some function before the debugger loads.
- Call some function after the debugger is done and closed.
- Call some function as part of debugger's button clicks. Note: This is a different ask from the first two.
|
Explore how to create a new side panel menu | - An option to choose specific icon.
- An option to register custom headers under the menu.
|
Explore the networking
Tasks | Expectation |
---|
Document the limitations for network connectivity, for different cases | Assumption: - Chaincode is always run via VS Code.
Cases: - Hyperledger Fabric is run locally on native machine.
- Hyperledger Fabric is run via the CRE (in a container environment).
- Hyperledger Fabric is run in a Kubernetes environment on local machine.
- Hyperledger Fabric is run on an external remote machine on the same sub-net.
- Hyperledger Fabric is run in another sub-net (could be a cloud environment).
|
Why are these experiments needed?
- As part of Fabric Chaincode Debugger VS Code plugin, connect to an existing Fabric network or bring up a custom Fabric network for debugging.
- Chaincode package and install to the Fabric network.
- Run the commands related to chaincode installation such as install, approve and commit.
- Decommission the chaincode upon closing the debugger.
Attendees
Varsha Pichandi
Claudia Emmanuel
Kent Lau
Chinmayi D S
Arun S M