Skip to content

Commit aa34a39

Browse files
authored
Use sub-bullets instead for change notice
1 parent 2e0f62d commit aa34a39

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
1-
## upcoming breaking changes
1+
## upcoming changes in v2
22

33
Near the end of March 2018, this plugin will update to v2 and will have a few minor breaking changes. This branch can be previewed at `v2` and should be stable.
44

5-
1. The filetype for playbooks will be set to `yaml.ansible`.
5+
- The filetype for playbooks will be set to `yaml.ansible`.
66
- 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.
77
- 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.
8-
2. `g:ansible_extra_syntaxes` will be 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`.
8+
- `g:ansible_extra_syntaxes` will be 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`.
99
- While this is a complete deprecation of one setting, the new functionality is significantly better all around and should support the same use-cases.
1010
- Example: a ruby+ansible-template will have a filetype of `ruby.jinja2` instead of `ansible_template`
11+
12+
One non-breaking change will also be added, this plugin will gain additional compatibility with _stephpy/vim-yaml_ — syntax highlights will be improved when using this plugin.
1113

1214
## introduction
1315

0 commit comments

Comments
 (0)