Skip to content

Compound filetypes
Compare
Choose a tag to compare
@pearofducks pearofducks released this 29 Mar 17:02
· 36 commits to master since this release
2.0
01d0e7d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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 of ansible_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.

Assets 2