I've created a new .d.ts file which will enable autocomplete whenever a particular global object is used in the code.
How do I package this .d.ts file as part of an extension, so that, anyone can install this extension and use the autocomplete/intellisense ?
Related
Here's what I want to achieve: I want to configure the extension so that it checks and fixes automatically any errors in any .scss file that I create.
I don't want to install the packages manually for every project that I create.
Here's what I've done so far:
Installed StyleLint Extension
Disabled VS Code's Built-In Linters
Installed the following packages globally:
Postcss
Postcss-scss
stylelint
stylelint-config-recess-order
stylelint-order
Enabled SCSS validation
Added path to postcss syntax
Any advice on what to do next?
The following repository contains a .juce file along with c++ source file. The operating system I am currently working on is Ubuntu. I want to be able to build this file into a .vst3 file so that it can be added as a plugin in any DAW which has that capability. When I open the .juce file in Projucer, it only lists Visual Studio 2017 as an exporter option, with no option to add exporters (usually for Linux, the options are Code::Blocks and Makefile). How do I build the source files here to create a .vst3 plugin file?
In the projucer application, if you click on the plus icon in the bottom left, you will get a menu with which you can specify which exporter configuration you want to add to the project.
After adding the linux makefile as an exporter configuration, you should save the projucer file which will generate the makefiles.
Then you can use "make" via terminal to compile the plugin in the specified formats.
Please make sure to enable the VST3 option in the settings page.
Is there any way using which we can force Visual Studio Code Marketplace extension to use our own configuration file instead of their own default .config file upon installation?
I really want to use my own configuration file for a particular something.
I basically have a similiar question to this one:
How can i configure clang format without .clang-format file in every workspace?
I'm using the Visual Studio Code editor (version 1.43) with the Clang-Format extension developed by Xaver (https://marketplace.visualstudio.com/items?itemName=xaver.clang-format#overview)
I adjusted the clang extension settings "Clang-format: Executable" option to point to the "clang-format.exe" of my VSC installation.
Furthermore I set "Clang-format: Style" to "file".
My clang-file is currently located inside my projects source folder.
As I want to use my clang settings for every project and don't want to copy the clang file into every project workspace manually (and maybe have to change every single copy later on), I tried to make the extension use a globally located clang-file which is inside the VSCs extention folder.
So my first approach was to relocate the clang-file into the "VSC 1.43\data" directory.
My second attempt was to locate it right inside the extension folder "C:\User\VSC 1.43\data\extensions\xaver.clang-format-1.9.0" where a default file was already present.
Unfortunately both attempts seem not to work. I can invoke the formatting with "Format Document" but another clang file seems to get utilized.
Only if I put the file back into the source code directory, my clang rules are getting utilized correctly.
So basically:
MyProject\SourceCode\clang-file --> Works
VSC\data\clang-file --> Doesn't work
VSC\data\extensions\xaver.clang-format-1.9.0\clang-file --> Doesn't work
Can I tell the extension to search for the clang file inside of the extensions installation directory instead of the current workspace?
Note: I just installed the clang-format extension and adjusted the mentioned extension settings above. I did not tamper with the VSC settings.json.
Thank you in advance and best regards :)
Evox402
As specified in the documentation:
When using -style=file, clang-format for each input file will try to find the .clang-format file located in the closest parent directory of the input file. When the standard input is used, the search is started from the current directory.
Actually I believe it searches for either .clang-format or _clang_format.
This explains:
MyProject\SourceCode\clang-file --> Works
You could move the .clang-format file to MyProject, or any parent directory above that, so that it is shared between projects.
In the plugins folder I see various languages and within those folders I see ticino.plugin.json file where file extensions are associated with the given plugin. However, PHP is not in this folder, and none of the ticino.plugin.json files have the PHP extension associated with them.
I do see in the client/vs/languages folder that there is php folder, but there is nothing that I can find that would allow me to associate the additional file extension.
I did similar, I cloned the c# plugin and renamed it, then added my extensions. Take a look, https://github.com/genecyber/connectiq-build