diff --git a/.vscodeignore b/.vscodeignore index 974eb15..dc529a8 100644 --- a/.vscodeignore +++ b/.vscodeignore @@ -13,3 +13,4 @@ vsc-extension-quickstart.md node_modules/** resources/functionalTests/** resources/samples/** +resources/treeSitterErrorTests/** diff --git a/package.json b/package.json index c5c9ceb..9f36527 100644 --- a/package.json +++ b/package.json @@ -1,10 +1,12 @@ { - "name": "AblFormatter", - "displayName": "AblFormatter", - "description": "TODO", + "name": "abl-formatter", + "displayName": "Abl Formatter", + "description": "Progress OpenEdge (ABL) code formatter", "version": "0.0.1", "icon": "resources/Formatter_LOGO.png", - "repository": {}, + "repository": { + "url": "https://github.com/BalticAmadeus/AblFormatter" + }, "engines": { "vscode": "^1.84.0" }, @@ -226,13 +228,7 @@ "description": "Enable table view with tree info on hover" } } - }, - "commands": [ - { - "command": "AblFormatter.helloWorld", - "title": "Hello World" - } - ] + } }, "scripts": { "copy-wasm": "copyfiles -u 2 ./node_modules/web-tree-sitter/*.wasm out", diff --git a/src/extension.ts b/src/extension.ts index 0627ff4..675e8b5 100644 --- a/src/extension.ts +++ b/src/extension.ts @@ -1,5 +1,3 @@ -// The module 'vscode' contains the VS Code extensibility API -// Import the module and reference it with the alias vscode in your code below import * as vscode from "vscode"; import Parser from "web-tree-sitter"; import { AblFormatterProvider } from "./providers/AblFormatterProvider"; @@ -10,8 +8,6 @@ import { ConfigurationManager2 } from "./utils/ConfigurationManager"; import { enableFormatterDecorators } from "./v2/formatterFramework/enableFormatterDecorators"; import { DebugManager } from "./providers/DebugManager"; -// This method is called when your extension is activated -// Your extension is activated the very first time the command is executed export async function activate(context: vscode.ExtensionContext) { const debugManager = DebugManager.getInstance(context); @@ -38,23 +34,9 @@ export async function activate(context: vscode.ExtensionContext) { const hoverProvider = new AblDebugHoverProvider(parserHelper); vscode.languages.registerHoverProvider(Constants.ablId, hoverProvider); - - // The command has been defined in the package.json file - // Now provide the implementation of the command with registerCommand - // The commandId parameter must match the command field in package.json - let disposable = vscode.commands.registerCommand( - "AblFormatter.helloWorld", - () => { - // The code you place here will be executed every time your command is executed - // Display a message box to the user - vscode.window.showInformationMessage( - "Hello World from AblFormatter!" - ); - } - ); - - context.subscriptions.push(disposable); } // This method is called when your extension is deactivated -export function deactivate() {} +export function deactivate() { + //do nothing +} diff --git a/vsc-extension-quickstart.md b/vsc-extension-quickstart.md deleted file mode 100644 index 04a57fc..0000000 --- a/vsc-extension-quickstart.md +++ /dev/null @@ -1,42 +0,0 @@ -# Welcome to your VS Code Extension - -## 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`. - -## 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 - -* [Follow UX guidelines](https://code.visualstudio.com/api/ux-guidelines/overview) to create extensions that seamlessly integrate with VS Code's native interface and patterns. - * Reduce the extension size and improve the startup time by [bundling your extension](https://code.visualstudio.com/api/working-with-extensions/bundling-extension). - * [Publish your extension](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) on the VS Code extension marketplace. - * Automate builds by setting up [Continuous Integration](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).