Mention v:t_TYPE variables in the developer documentation
This commit is contained in:
parent
daab1a08db
commit
a7b8cb4fe3
1 changed files with 1 additions and 0 deletions
|
@ -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.
|
||||||
|
|
||||||
|
|
Reference in a new issue