Skip to content
This repository has been archived by the owner on Mar 31, 2023. It is now read-only.

Latest commit

 

History

History
65 lines (51 loc) · 2.26 KB

CHANGELOG.md

File metadata and controls

65 lines (51 loc) · 2.26 KB
Raw

Change Log

All notable changes to the Ansible VS Code extension will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[1.2.0] - 2022-02-06

Added

  • Deprecation notification, and migration guide.

[1.1.0] - 2021-11-14

Added

  • Nested module options (aka sub-options) are now supported!

[1.0.8] - 2021-09-25

Fixed

  • Options and other documentation parts are now also recognized when the module includes them via non-default documentation fragment properties (ie. other than the DOCUMENTATION property).

[1.0.7] - 2021-09-06

Fixed

  • Paths with very special characters (such as @) now handled correctly too.

[1.0.6] - 2021-08-10

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.

[1.0.5] - 2021-08-08

Fixed

  • Files with CRLF line endings will now display and behave correctly. No more weirdly offset highlighting and interactions.

[1.0.4] - 2021-08-04

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.

[1.0.3] - 2021-07-27

Changed

  • Error handling in case output from Ansible Lint can't be parsed is now more informative. Contextual information is now logged in Ansible Server output.

[1.0.2] - 2021-07-19

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.

[1.0.1] - 2021-07-15

Fixed

  • Documentation fragments are now also correctly processed in case only one is provided, using YAML flow style. The file module is a prominent example.

[1.0.0] - 2021-07-14

  • Initial release