From a7b8cb4fe32b43dbeeadc8cb94f378b4e2112723 Mon Sep 17 00:00:00 2001
From: w0rp <devw0rp@gmail.com>
Date: Fri, 27 Jul 2018 09:18:09 +0100
Subject: [PATCH] Mention v:t_TYPE variables in the developer documentation

---
 doc/ale-development.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/ale-development.txt b/doc/ale-development.txt
index 8a4c1d7d..d83c98f2 100644
--- a/doc/ale-development.txt
+++ b/doc/ale-development.txt
@@ -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
   variable names. You can define `aliases` for linters, for other names people
   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.