Skip to content
This repository has been archived by the owner on Oct 9, 2024. It is now read-only.

Sync with upstream #7

Merged
merged 4 commits into from
Aug 25, 2021
Merged

Sync with upstream #7

merged 4 commits into from
Aug 25, 2021

Conversation

tomaciazek
Copy link
Contributor

This pull request synchronizes the language server implementation with the changes made to https://github.com/tomaciazek/vscode-ansible since fork.

Since ansible-lint is executed from the root directory of the workspace
the algorithm that it uses to find configuration for a particular file
is not involved. To compensate, the extension now mimics that behavior,
searching the directory structure, going up from the investigated file.

At the same time, it is still possible to force a particular config file
through arguments provided in the extension settings.

The configuration file that is actually used is now correctly identified
for the purpose of marking configured finding groups as warnings.
@ganeshrn
Copy link
Member

Thank you!

@ganeshrn ganeshrn merged commit c00347f into main Aug 25, 2021
priyamsahoo referenced this pull request in priyamsahoo/ansible-language-server Sep 15, 2021
* Fix special characters in workspace and file paths (#15)

* Advise yamllint installation and use (#16)

* Fix handling of files with CRLF line endings (#20)

* Mimic linter's config file search algorithm (#22)

Since ansible-lint is executed from the root directory of the workspace
the algorithm that it uses to find configuration for a particular file
is not involved. To compensate, the extension now mimics that behavior,
searching the directory structure, going up from the investigated file.

At the same time, it is still possible to force a particular config file
through arguments provided in the extension settings.

The configuration file that is actually used is now correctly identified
for the purpose of marking configured finding groups as warnings.
@ssbarnea ssbarnea deleted the sync_with_upstream branch October 13, 2021 11:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants