Environment :

• Windows 10
• VS code : 1.5.4.2
• VScode salt-lint : 0.0.5 (default conf)
• salt-lint : 0.5.2 (installed from python 3.8.0)

With this configuration nothing is displayed in my sls file under VSC.
Command line is OK

I have a working configuration only with salt-lint 0.4.2 (all versions > 0.4.2 doesn't work).

Thank you

While installing warpnet.salt-lint from the command using code --install-extension warpnet.salt-lint the following error is shown:

(node:3733) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

Hi,

I am facing an issues on VScode on Windows, that salt-lint is not found after start. Full error:

Cannot salt-lint the Salt State file. The salt-lint program was not found.

It is strange, because integrated VScode terminal can use salt-lint Python binary and use linter on file using cli, it can also be called directly from Windows Terminal. I see this error only when running this extenstion. BTW VScode is not running under Administrator and I have path to Python scripts added to ENV variables. Could you help me what need to be checked? Thanks.

Enabling vscode-salt-lint breaks syntax highlighting in korekontrol/vscode-saltstack. This is probably caused by a mismatch in the language ID. This extension uses saltstack while korekontrol/vscode-saltstack uses sls as the language ID.

Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please sign the Eclipse Publisher Agreement on or before January 8, 2021. If not signed by that date, your extensions will be delisted and will no longer appear on the site nor be available via the API. If you sign at a later date, your extensions will then be re-activated. The signing process is explained in the Wiki (steps 1 and 2).

Please also note that all extensions MUST have a license in order to be listed.

More details are in these recent blog posts:
https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management
https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry

Today, there’s growing momentum around open source tools and technologies that support Visual Studio (VS) Code extensions. Leading global organizations are adopting these tools and technologies. This momentum has spurred demand for a marketplace without restrictions and limitations. Thanks for joining us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!

I did eventually locate salt-lint, but it would have been very helpful to have a link to it directly in the README.

After updating salt-lint to 0.4.0 or 0.4.1 linting errors in VSCode do not appear, by downgrading to 0.3.0 linting issues appear again.

It would be nice if the extension could read a .salt-lint config file from the following locations. Preference would be from first to last.

• Project root folder
• User home directory
• OS dependent config folder (i.e. Linux ~/.config/...., Windows c:\Users\username\AppData...., MacOS ~/Library/Application Support/....)

Here's an example of a .salt-lint file: https://github.com/saltstack-formulas/openssh-formula/blob/master/.salt-lint

Hello Warpnet!
I installed salt-lint as described, using pip3. It works fine on the CLI, but this extension gives command 'salt-lint.runLint' not found every time I try to run it from the "Command Palette".

Any clues on how to fix or debug this issue?

Feature request to provide a mechanism to ignore specific lint recommendations globally instead of per line. For the example above, it is desirable to ignore this, however the only mechanism is to comment "# noqa: xxx" on that specific line:

/tmp/testfile:
  file.managed:
    - source: salt://{{unspaced_var}}/example  # noqa: 207

The version on open-vsx.org isn't up to date. I know I would appreciate it if you were to update it for those using vscodium.

Add GitHub workflow to automatically release the extension to VS Code Marketplace.

Relevant code:

On my system, with both saltstack and salt-lint installed, I get syntax highlighting and lint information. However, it seems that there is an intent to provide links to the wiki in the extension code, which does not pop up at all.

I stumbled onto this while trying to research how quickfix actions work and if it would be possible for me to start implementing some for basic things like salt-lint(207) and salt-lint(208). On that note, if you have any information that might be a good starting point I would love some pointers!!

Edit: I see this seems to be the spec for quickfix actions: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_codeAction

Add GitHub workflow to automatically release the extension to Open VSX.