Adding colorizer tests to an extension - visual-studio-code

My team and I built a colorizer extension that highlights colors in the logging output in VSCode. In the core extensions there are colorize tests that get called automatically with VSCode since they are bundled in.
I was wondering how to call the colorize tests for an extension that is not bundled in VSCode.
Source code available here.

Related

Does VS Code install some extensions automatically?

I noticed that I have many extensions installed that I don't recall manually installing, e.g. isort, jupiter cell tags, etc.
I only installed the "python" and "jupyter notebooks" extensions myself. Those others seem to be installed later without my knowledge.
Does VS Code install extensions automatically somehow?
To answer the general question
Yes, VS Code does come with some extensions installed "out-of-box". It calls those extensions "Built-In" extensions. If you open the extension page of one of those extensions, it will say:
Notice: This extension is bundled with Visual Studio Code. It can be disabled but not uninstalled.
One example of this is the vscode.typescript-language-features extension. You can get a list of all running with the Developer: Show Running Extensions command. It's kind of hard to find them otherwise, since they don't normally show up in the extensions sidebar.
In your particular case, you misunderstood something
The Python and Jupyter extensions you installed are extension packs. They include isort and Jupyter Cell Tags (as well as others).
You can see for yourself.
https://marketplace.visualstudio.com/items?itemName=ms-python.python:
The Python extension will automatically install the Pylance, Jupyter and isort extensions to give you the best experience when working with Python files and Jupyter notebooks.
https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter:
The Jupyter Extension will automatically install the following extensions by default to provide enhanced Jupyter notebook experiences in VS Code.
Jupyter Keymap - to provide Jupyter-consistent keymaps
Jupyter Notebook Renderers - to provide renderers for MIME types such as latex, plotly, vega, etc.
Jupyter Cell Tags and Jupyter Slide Show - to provide the ability to tag cells in notebooks and support for presentations

VS Code JavaScript Hint

I am new to VS Code. HTMLHint extension shows hints live without a need to run a separate process.
I have used ESLint & JSHint in browser environment (Web or browser extension) and both show hints live.
I installed ESLint extension and it seems that it requires nmp & running a separate process to check the syntax.
Don't they run automatically like HTMLHint or Spell checker extensions?
How can syntax errors and/or suggestions be shown in VS Code?

Install VS Code extension during development?

I am developing an extension for VS Code. This extension is already good enough for me to use during daily work, but not good enough to be published (yet). Is there a canonical way to make an unpublished extension under development available to VS Code? Optimally, I would like to always have the current state of the code running.
I did find a way that seems to work, but I'm not sure whether this is a terrible hack or okay: Create a symbolic link in VS Code's extensions directory (~/.vscode/extensions on Linux) to the development directory. Is there a better/official way?
You can package your extension (even if it's in development) using vsce with the command vsce package. This will create a .vsix file which you can install in your regular instance of VSCode in the marketplace menu (click on the ... icon at the top and select "Install from .vsix file).
If you need to view the logs of the extension, go to Help>Toggle Developer tools and use the console to view your extension's output (if there is any).

Visual Studio Code language extension not highlighting syntax

Followed this piece of instruction to create a language extension for .abcd files.
During yeoman generator I used this as a reference.
Everything went well and the new extension was created. Then I open the generated folder as a Visual Studio project and hit F5 to run VS Code with my newly created extension, but nothing gets highlighted as if there is no support for that language.
I have not done any changes to the generated files, but since I am using Ada.plist as a starting point, shouldn't it at least highlight .abcd file as Ada file?
You need package.json file to register the language. It's described in the same document.
You may be interested in this repo also:
https://github.com/Entomy/Ada-vscode

Is it possible to have Visual Studio Code custom configured from a .ps1 file?

I'm attempting to put together a standard VS Code build for my company. I have a ps1 file that copies/installs extensions for VS Code after it's been installed but I can't seem to find how or even if it is possible to then configure VS Code settings to utilize those extensions.
For example, one of the extensions is "vscode-icons". I can install the extension just fine but then the user needs to setup his preferences manually to actually use the extension by going to the File->Preferences->File Icon Theme->VS Code Icons.
Is it possible to have my ps1 install file actually make configuration changes so any user who opens VS Code has the custom configuration settings?
The config settings for VS Code are JSON files - just needs to locate and edit them.
First check what manual change is doing then create part in the script to edit the settings.
https://code.visualstudio.com/docs/customization/userandworkspace