This repository has been archived by the owner on Mar 31, 2023. It is now read-only.
Releases: tomaciazek/vscode-ansible
Releases · tomaciazek/vscode-ansible
v1.2.0
v1.1.0
Added
- Nested module options (aka sub-options) are now supported!
v1.0.8
Fixed
- Options and other documentation parts are now also recognized when the module
includes them via non-default documentation fragment properties (ie. other
than theDOCUMENTATION
property).
v1.0.7
Fixed
- Paths with very special characters (such as
@
) now handled correctly too.
v1.0.6
Changed
- The configuration file for Ansible Lint is now identified by going up the
directory structure, starting from the investigated file, and taking the first
.ansible-lint
file encountered. This effectively mimics the algorithm
implemented natively in the linter, while still executing it from the root
folder of the workspace.
v1.0.5
Fixed
- Files with CRLF line endings will now display and behave correctly. No more
weirdly offset highlighting and interactions.
v1.0.4
Fixed
- Paths with special characters are now correctly handled. Both in case of
workspace path and in case of files in workspace.
Changed
- Now encouraging to install
yamllint
as it has been tested and it provides
useful additional advice on YAML files.
v1.0.3
Changed
- Error handling in case output from Ansible Lint can't be parsed is now more
informative. Contextual information is now logged inAnsible Server
output.
v1.0.2
Fixed
- Modules from pre-installed Ansible collections will now be resolved when using
the extension in an environment that also has Python 2 installed. - The cause of the
invalid syntax
error shown on startup has been removed.
v1.0.1
Fixed
- Documentation fragments are now also correctly processed in case only one is
provided, using YAML flow style. Thefile
module is a prominent example.