I have WebStorm with ESLint enabled and it's working fine.
But from VS Code I'm used to see the eslint output window for the whole project I'm working on, not only for the current file (and hidden inside the scrollbar)
I cannot figure out how to do this in WebStorm - is it even possible?
You can see all errors coming from ESLint in Inspection Results tool window that opens when you run Analyze/Inspect Code:
Related
I am trying to format my code using Prettier, but when I try to format it by saving the file, by clicking "Format document with" or by any other way it just doesn't format and the Prettier button turns red and appears this ! icon.
I reinstalled VS Code and Prettier hundreds of times. Any idea of how I can fix this?
Here are the images of what is happening:
Image of the red button:
When I click, it returns to its normal color, but nothing happens
There are two cases here, you're either working on a:
non-Node project (doesn't have package.json) - delete any unnecessary package.json files from current folder and immediate parent folders.
Node.js project (contains package.json file) - Run npm install, or npm install prettier --save-dev (in the terminal at the folder level) if it still doesn't work.
I had the same problem. In my case, I had a useless package.json file in the parent folder, which was causing all the issue. I was working on a simple HTML, CSS and JS project.
Does anyone know how to have GoLand constantly inspecting errors in code? Right now it inspects ONLY the open files and shows the status on the top-right corner like this:
But in VS Code, it constantly checks all errors of the working module.
GoLand does offer manual inspection but it's not as efficient and often checks irrelevant modules too (when I set it current module then it can't detect any errors)
As mentioned in Goland issue GO-4618:
They might be limiting the contents of the Problems tool window to just the current editor for performance and usability reasons.
GO 9494 is following the issue: "Customize Problems View reporting scope"
There should be a way to customize the Problems View window to support the following scopes:
Current File
Current File's Package (I'd default to this)
All Opened Files Packages
Whole Project (IDEA-68854)
Still in progress (oct. 2021) though.
I am doing leetcode exercises on vscode, using this extension:
However vscode keeps sending error notifications about the golang codes written locally lack of main module
How can I disable vscode error notifications? As those golang codes are used to run remotely, so there are no needs to compile locally
Check first if you can disable the Go extension, just for your current (leetcode) workspace.
If you don't want to permanently remove an extension, you can instead temporarily disable the extension by clicking the gear button at the right of an extension entry.
You can disable an extension globally or just for your current Workspace.
You will be prompted to reload VS Code after you disable an extension.
By disabling it just for the workspace, you can still use Go for Go projects in a separate workspace in the same VSCode.
So my understanding from the documentation to perform a publish is I need to call 'electronize build /target win'. This builds the project. However, there are some issues I'm unsure how to address.
The content path when I try to run it says the content root is C:\Windows\system32 instead of the actual working directory where the .exe resides. That isn't correct. Any ideas why? I think some of the other issues are caused by this.
Edit: I found out #1 uses the correct directory if it is ran as administrator. Unsure why.
How does one hide the command menu that comes up? all i want is the electron window to show on publish.
I see an electron window come up like when i run 'electronize start' but not after publishing. Any ideas?
Please try the latest version of Electron.NET. During development, a development menu is displayed. A standard behavior of Electron if you not have your own menu. With a build, the development menu is hidden again.
Visual Studio Code (0.3.0 - 0.7.0) defaults to opening files in a new window, so if you double-click a file in the project view in Unity, or any log in the console, it will open a new window rather than opening the file in an existing window you already have open.
Visual Studio Code (0.5.0 - 0.7.0) will open a file in an existing window if you pass it the command line arg -r, however Unity will not let you customize command line arguments on OSX, it's a Windows-only feature.
Is there a way to open files from Unity into an existing window in Visual Studio Code (0.3.0 - 0.7.0)?
There is a way, but it's a pain. Create a shell script that calls Visual Studio Code and passes it the file path that Unity provides:
"/Applications/Visual Studio Code.app/Contents/MacOS/Electron" -r -g $1
exit 0
Then you need to make an .app from that shell script. I used a program called Platypus to make the .app. If you use Platypus make sure to check the 'Accepts Dropped Items` checkbox, it didn't work for me until I used this option.
Once you have the .app created you need to set that app as your External Editor in Unity.
Hopefully in the future Unity will allow custom arguments to be sent for OSX, not just Windows. Also it would be nice if Unity passed the line and column numbers to custom external editors, currently those details are only passed to certain Unity-recognized editors. There is really no reason I can think of that why they could not pass that information as additional arguments. Because that information isn't being passed that means you cannot configure this script to open up the file to line that an error might be on, which is a bummer.
Also, this entire answer would be unnecessary if the Visual Studio Code team would just add an option in the preferences to default to opening files in the existing window instead of defaulting to a new one. There are a couple of feature requests listed on their site for this currently, here's one: http://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/8740771-persistant-option-to-open-files-in-existing-window
Hi you can get full debugging support in VSCode for Unity using this plugin
https://github.com/dotBunny/VSCode
VS Code in Unity
This plugin works on both MacOS and Windows and gives you the following capabilities:
•An option to enable VS Code integration (Editor –> Assets –> Enable Integration), this updates your solution files and (more importantly) keeps them in sync. This also sets the preferred external tool editor in the Unity preferences.
*Note, the old “Sync MonoDevelop” option is now gone in the Unity editor from V5.2
•It writes out the necessary (and sometimes hard to find) VS Code configuration files, including the ability to hide “non-code” files in the editor (hides things like .sln, .csproj and the ever present unity .meta files)
There are a couple of other settings in there to help speed up the integration.
•Automatically launches VS Code direct to your project folder, EVERY-TIME. no longer do you have to worry about keeping that window open, or switching around if you work on multiple projects
One thing to be aware of, once you enable the VSCode integration, changing your preferred code editor in the External Tools preferences will have no effect as the plugin takes over opening code files.