vim/ale
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Mention v:t_TYPE variables in the developer documentation

Browse Source
This commit is contained in:
w0rp 2018-07-27 09:18:09 +01:00
parent daab1a08db
commit a7b8cb4fe3
No known key found for this signature in database
GPG Key ID: 0FC1ECAA8C81CD83
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/ale-development.txt
View File

@ -118,6 +118,7 @@ these are reported with ALE's `custom-linting-rules` script. See
* Use `snake_case` names for linter names, so they can be used as part of * Use `snake_case` names for linter names, so they can be used as part of
variable names. You can define `aliases` for linters, for other names people variable names. You can define `aliases` for linters, for other names people
might try to configure linters with. might try to configure linters with.
* Use |v:t_TYPE| variables instead of `type()`, which are more readable.
Apply the following guidelines when writing Vader test files. Apply the following guidelines when writing Vader test files.