Skip to content

Aincvy/vscode-fauxpilot

This branch is 17 commits ahead of, 7 commits behind Venthe/vscode-fauxpilot:main.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Jun 1, 2024
bdfa86a · Jun 1, 2024

History

94 Commits
Mar 31, 2023
Aug 8, 2022
Mar 31, 2023
Sep 24, 2023
Jan 3, 2024
Aug 8, 2022
Aug 8, 2022
Aug 8, 2022
Mar 31, 2023
Aug 8, 2022
Jun 1, 2024
Sep 22, 2023
Jun 1, 2024
Aug 8, 2022
Aug 8, 2022

Repository files navigation

Visual Studio Code - Fauxpilot Client

vs code ext store link: https://marketplace.visualstudio.com/items?itemName=Aincvy.fauxpilotaincvy

Support server list:

Development

Copied from VSC extension guidelines

What's in the folder

  • This folder contains all of the files necessary for your extension.
  • package.json - this is the manifest file in which you declare your extension and command.
    • The sample plugin registers a command and defines its title and command name. With this information VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
  • src/extension.ts - this is the main file where you will provide the implementation of your command.
    • The file exports one function, activate, which is called the very first time your extension is activated (in this case by executing the command). Inside the activate function we call registerCommand.
    • We pass the function containing the implementation of the command as the second parameter to registerCommand.

Setup

  • install the recommended extensions (amodio.tsl-problem-matcher and dbaeumer.vscode-eslint)

Get up and running straight away

  • Press F5 to open a new window with your extension loaded.
  • Run your command from the command palette by pressing (Ctrl+Shift+P or Cmd+Shift+P on Mac) and typing Hello World.
  • Set breakpoints in your code inside src/extension.ts to debug your extension.
  • Find output from your extension in the debug console.

Make changes

  • You can relaunch the extension from the debug toolbar after changing code in src/extension.ts.
  • You can also reload (Ctrl+R or Cmd+R on Mac) the VS Code window with your extension to load your changes.

Explore the API

  • You can open the full set of our API when you open the file node_modules/@types/vscode/index.d.ts.

Run tests

  • Open the debug viewlet (Ctrl+Shift+D or Cmd+Shift+D on Mac) and from the launch configuration dropdown pick Extension Tests.
  • Press F5 to run the tests in a new window with your extension loaded.
  • See the output of the test result in the debug console.
  • Make changes to src/test/suite/extension.test.ts or create new test files inside the test/suite folder.
    • The provided test runner will only consider files matching the name pattern **.test.ts.
    • You can create folders inside the test folder to structure your tests any way you want.

Go further

Acknowledgements

Inspired & used snippets from:

Client is build around Fauxpilot server

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript 94.4%
  • JavaScript 5.6%