This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Contributions are always welcome! We only ask that you open an issue first so we can discuss the problem and solution. We don't want you to waste any time headed in the wrong direction.
- Clone this repo
- Run
npm installin '/vscode-edge-devtools' - Run
npm run buildornpm run watchin '/vscode-edge-devtools' - Open the directory in VS Code
- Select
Launch Extensiondebug configuration - Press
F5to launch the VS Code extension host environment and debug the extension - The extension should appear on the left sidebar. Click the Edge icon on the sidebar to access the extension.
Here are a list of recommended VS Code extensions to use when developing for vscode-edge-devtools:
- There are a set of jest tests which can be run with
npm run test. - You may also run
npm run lintseparately to check your code against our tslint rules. - Open the directory in VS Code
- Select
Launch Testsdebug configuration - Press
F5to attach the debugger and start the tests
- "Bug": Something that should work is broken
- "Enhancement": AKA feature request - adds new functionality
- "Task": Something that needs to be done that doesn't really fix anything or add major functionality. Tests, engineering, documentation, etc.