Releases: pearofducks/ansible-vim
3.4
3.3
What's Changed
- Add missing keyword: children. by @xoraxiom in #123
- Ftdetect control filenames by @henrik-farre in #125
- indent: default to the result of GetYAMLIndent; always return the def… by @alan-strohm in #127
- UltiSnips: add an option to remove options decriptions. by @gjherbiet in #128
- UltiSnips: add an option to comment non-required options. by @gjherbiet in #129
- Search collections installed via package manager as well by @stove-panini in #130
New Contributors
- @xoraxiom made their first contribution in #123
- @henrik-farre made their first contribution in #125
- @alan-strohm made their first contribution in #127
- @gjherbiet made their first contribution in #128
- @stove-panini made their first contribution in #130
Full Changelog: 3.2...3.3
Syntax keywords update, new config flag available
ansible_with_keywords_highlight
is soft-deprecated (there is backwards compatibility in place for now), and is replaced withansible_loop_keywords_highlight
which aligns better with modern Ansible keywords for loops- Keywords that have been removed from Ansible are no longer highlighted, and new keywords in latest Ansible are added
FQCN snippet generation
Thanks to @pescobar the snippet-generation script now supports fully qualified collection names when used against Ansible 2.10 or greater.
https://docs.ansible.com/ansible/latest/user_guide/collections_using.html
Reproducible UltiSnip snippets - drop Python 2 support
Breaking: Drops Python 2 support in UltiSnip generation
Change: Makes the UltiSnip snippets generation reproducible
Add 'loop' keyword
Add highlighting for the loop
keyword, which has been available since Ansible 2.5.
https://docs.ansible.com/ansible/latest/user_guide/playbooks_loops.html
Minor fixes and improvements
Notable changes:
- python3 support added to the UltiSnip
generate.py
, as well as Mac Homebrew support - an old
regexpengine
workaround was removed that was breaking some setups
Otherwise there were minor fixes included in this changeset.
Compound filetypes
The filetype for playbooks is now set to yaml.ansible
.
- Using a compound filetype here improves compatibility with some other plugins, and is a bit more honest about the filetypes being used. We could set it to
yaml.jinja2.ansible
, if there are strong opinions on this please open an issue. - This only breaks setups using vim plugin on-demand loading features — e.g.
{ 'for': 'ansible' }
in vim-plug. Otherwise this change should not break anything.
g:ansible_extra_syntaxes
is deprecated in favor of g:ansible_template_syntaxes
— which will use conditional compound filetypes, instead of sourcing all filetypes listed and hiding them under ansible_template
.
- While this is a complete deprecation of one setting, the new functionality is significantly better all around and should support the same use-cases.
- Example: a ruby+ansible-template will have a filetype of
ruby.jinja2
instead ofansible_template
One non-breaking change is also added, this plugin gains additional compatibility with stephpy/vim-yaml — syntax highlights will be improved when using this plugin.
ansible-only filetype
DEPRECATED
This is the last version using ansible
as the filetype for Ansible playbooks. This tag is created as a convenience for anyone to branch from or keep as their plugin target.
1.0
Changes:
hosts
files are now highlighted with our own rules, rather than usedosini
rules. This allows for much better treatment of variables and Ansible's special categories (e.g. [foo:vars]).