bug in pulsar/ide-ui causing issues displaying yaml syntax message update error-line-col, bad_include, missing_include because syntax-check no longer finding errors in general js bug causes matchesYAMLError[1] message to not be captured (yaml_syntax fixture)
- Improve YAML syntax error message parsing.
- Ignore irrelevant inventory and hosts warnings.
- Workaround JS bug returning incorrect conditional on YAML error.
- Updates to Linter API usage.
- Fix error catch exec return.
- Fix warning file location.
- Bump minimum supported version to 2.0.
- Deal with when Ansible fails to determine issue location.
- Change linter scope to project level.
- Capture new wording in output describing file with error.
- Only parse for one error in output (efficiency improvement).
- Updated
atom-linter
dependency. - Catch linting on nonexistent files.
- Added
ansible-advanced
to source scope.
- Switched to using Linter v2 API.
- Removed
atom-package-deps
dependency and functionality.
- Config description additions.
- Earlier termination on non-playbook files.
- Now uses
ansible.cfg
located in directory of playbook if it exists. - The host inventory config setting is now used only when a custom value is entered.
- Added option for using an Ansible-Vault password file while linting.
- Fixed undefined return for non-playbook Ansible files.
- Removed range 1 where unnecessary.
- Errors for files which are included or roles from the playbook are now displayed.
- Updated
atom-linter
dependency. - Linter now ignores includes and roles.
- Added severity key.
- Removed option to lint all yaml by default since
language-ansible
now identifies all.yml
as Ansible.
- Added support in configuration for extra variables and module paths.
- Line and column information now displayed for situations when
ansible-playbook
guesses it. - Warnings and deprecation warnings are now displayed.
- Minor code optimization.
- Initial version ready for wide usage.