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

Conversation

@yaegassy
Copy link
Contributor

@yaegassy yaegassy commented Sep 16, 2021

Description

I thought it would be useful to add "prepare" so that yarn or yarn install alone would also build.

If you have not intentionally set "prepare", Please close this PR. 🙇

DEMO (mp4)

ansible-ls-add-prepare.mp4

@ganeshrn ganeshrn requested review from a team and tomaciazek September 16, 2021 04:02
@ganeshrn
Copy link
Member

@yaegassy Thanks for the PR.
I came across your coc.nvim extension. Nice work!

If you want to discuss/share feedback about ansible-language-server or extension the maintainers do hang out in the IRC channel #ansible-devtools and same channel in the matrix room.

@ssbarnea
Copy link
Member

@yaegassy I will need to close this PR because we removed yarn support in #22, if we need a prepare it should be for npm.

Also let me first thank you for writing an extension for nvim users. While I am not one of them I do know how important it is. Feel free to add a PR to list your extension inside the readme. I hope that soon we will be able to have the testing setup and be able to check if language server changes do impact users of it (IDE extensions).

@ssbarnea ssbarnea closed this Sep 16, 2021
@yaegassy
Copy link
Contributor Author

yaegassy commented Sep 16, 2021

@yaegassy I will need to close this PR because we removed yarn support in #22, if we need a prepare it should be for npm.

OK!

ekmixon pushed a commit to ekmixon/ansible-language-server that referenced this pull request Oct 15, 2021
* Fix special characters in workspace and file paths (ansible#15)

* Advise yamllint installation and use (ansible#16)

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

* Mimic linter's config file search algorithm (ansible#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.
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.

3 participants