Research steps involved in building a VS Code plugin

[arsulegai]

The expectation here is to document, and the relevant links from the VS Code's documentation, including sample codebase. The ask is to create a sample plugin that would print "Hello World".

An individual task list can be created as a research activity for each of the following.

Note:

1. Identify and document any system dependencies. For instance, VS Code plugin while working on Mac vs Windows. The finding could be in terms of the default configurations, the system dependencies.
2. Research how to run the codebase, along with opening of port. Imagine running chaincode as a service, remotely connecting to an existing blockchain network.
3. Research how to pass a configuration file to the code at runtime. Checkout the "Debugger Extension" at https://code.visualstudio.com/api/extension-guides/debugger-extension . Would it be possible to pass a runtime configuration file here? How to deal with such complexity when multiple configuration files are passed?

[literalEval]

Hey @arsulegai . I am Ravi Dev Pandey, pursuing my final year at Indian Institute of Technology, Varanasi, India.

I have worked extensively with Code Editor Integration during my Google Summer of Code period last year, where I built a doc checker, custom linter, and quick fix for the codebase.

I would love to use my knowledge of plugin development for this project. Thanks.