New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report if ansible-lint is broken #57
Comments
I was going to work on this, but there's already a little error popup.
If pointing to the ansible-lint in a venv without pointing the rest of the extension to the venv:
I think this issue already done? |
@ssbarnea, @lilatomic This PR: ansible/ansible-language-server#5 takes care of the following issue. If there is some problem in installation or configuration of ansible-lint, it reports the user and falls back to --syntax-check. |
ansible-lint does not work with this extension but works with a previous extension below. https://marketplace.visualstudio.com/items?itemName=tomaciazek.ansible The previous one shows red error with ansible-lint as below. However, this extension does not with the same setting. I set ansible.path, ansibleLint.path, and python.interpreterPath, but does not work. Other features such as autocompletion are working. My environment is below.
I hope to use ansible-lint with new extension as previous one is deprecated. |
The Ansible extension 0.7.1 still doesn't have ansible-lint integration working, as @yoshiotobe demonstrated above.
Update: works with extension 0.8.1 and |
* update module completion return statement to support fqcn returns whenever necessary * fix order of priority in filtering of text when FQCN is used Co-authored-by: Sorin Sbarnea <ssbarnea@redhat.com>
As ansible-lint have very special requirements for running, we need to be sure that we run
ansible-lint --version
and report any potential error in a visible way in the UI.This should make it easier for users to debug broken or incomplete installs of ansible-lint tool.
Related: ansible/ansible-lint#1507
The text was updated successfully, but these errors were encountered: