From f80ad9010647321039757de628c857038a46c227 Mon Sep 17 00:00:00 2001 From: alemi Date: Fri, 6 Sep 2024 14:17:17 +0200 Subject: [PATCH] chore: disabled rust CI, removed leftover stuff --- .cargo/config | 6 ------ .github/workflows/ci.yml | 31 --------------------------- .rustfmt.toml | 1 - tsconfig.json | 2 +- vsc-extension-quickstart.md | 42 ------------------------------------- 5 files changed, 1 insertion(+), 81 deletions(-) delete mode 100644 .cargo/config delete mode 100644 .github/workflows/ci.yml delete mode 100644 .rustfmt.toml delete mode 100644 vsc-extension-quickstart.md diff --git a/.cargo/config b/.cargo/config deleted file mode 100644 index e09164b..0000000 --- a/.cargo/config +++ /dev/null @@ -1,6 +0,0 @@ -[net] -git-fetch-with-cli = true - -[target.aarch64-unknown-linux-musl] -linker = "aarch64-linux-musl-gcc" -rustflags = ["-C", "target-feature=-crt-static"] diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml deleted file mode 100644 index c165435..0000000 --- a/.github/workflows/ci.yml +++ /dev/null @@ -1,31 +0,0 @@ -name: Cargo Build & Test - -on: - push: - branches: - - dev - - main - -env: - CARGO_TERM_COLOR: always - -jobs: - build_and_test: - name: Rust project - latest - runs-on: ubuntu-latest - strategy: - matrix: - toolchain: - - stable - # - beta - # - nightly - # disable other toolchains to save on github runners - steps: - - uses: arduino/setup-protoc@v2 - - uses: actions/checkout@v3 - - uses: webfactory/ssh-agent@v0.7.0 - with: - ssh-private-key: ${{ secrets.ACTIONS_SSH_DEPLOY_KEY }} - - run: rustup update ${{ matrix.toolchain }} && rustup default ${{ matrix.toolchain }} - - run: cargo build --verbose - - run: cargo test --verbose diff --git a/.rustfmt.toml b/.rustfmt.toml deleted file mode 100644 index 218e203..0000000 --- a/.rustfmt.toml +++ /dev/null @@ -1 +0,0 @@ -hard_tabs = true diff --git a/tsconfig.json b/tsconfig.json index c6d14f6..315af7e 100644 --- a/tsconfig.json +++ b/tsconfig.json @@ -13,5 +13,5 @@ // "noImplicitReturns": true, /* Report error when not all code paths in function return a value. */ // "noFallthroughCasesInSwitch": true, /* Report errors for fallthrough cases in switch statement. */ // "noUnusedParameters": true, /* Report errors on unused parameters. */ - }, + } } 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).