-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
changed the name of the extension, updated README and packaged the ex…
…tension as " activedoc-0.0.1.vsix"
- Loading branch information
Showing
4 changed files
with
37 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,30 @@ | ||
# first-extension README | ||
# activeDoc Extension for VSCode | ||
|
||
This is the README for your extension "first-extension". After writing up a brief description, we recommend including the following sections. | ||
This is the README for the "activeDoc" extension for VSCode. | ||
|
||
# VSCode Extension doesn't have recentSearchedKeywords array | ||
## version 0.0.1.vsix state | ||
- The search keywords of a vscode workspace is not accessible to the VSCode API users. So, `searchedElements` property is not present in the vscode extension | ||
- In mac, clicking on a code snippet on the client (web) app is not redirecting the vscode workspace focused file's intended code snippet as it should. | ||
|
||
# running the extension | ||
after cloning the repo, open terminal and run "npm install" | ||
then in the vscode, you can press F5 to run the extension, or there should be a button in the left side of the vscode that looks like | ||
a beetle under the play icon called "Run and Debug". | ||
Clicking on it you should see green play icon. | ||
After that you can refresh the client. | ||
## Features | ||
|
||
- Describe the key features. | ||
- Explain how these features improve the user experience or development process. | ||
|
||
## Installation | ||
|
||
### Running the Extension Codebase | ||
|
||
1. After cloning the repo, open a terminal in the project directory. | ||
2. Run `npm install` to install the necessary dependencies. | ||
3. To run the extension in a development environment, press `F5` in VSCode, or click on the "Run and Debug" icon (resembles a beetle under the play icon) on the left sidebar. Then, click on the green play icon to start. | ||
|
||
### Installing the Packaged Extension | ||
|
||
To install the `.vsix` packaged extension: | ||
|
||
1. Open VS Code. | ||
2. Go to the Extensions view by clicking on the square icon on the sidebar or pressing `Ctrl+Shift+X`. | ||
3. Click on the "..." menu at the top of the Extensions view and select "Install from VSIX...". | ||
4. Navigate to the `.vsix` file, select it, and click "Open". | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters