From 6f7dfc3c691c3f56044814616e7cdd24b78721e3 Mon Sep 17 00:00:00 2001 From: Andrei Selkin Date: Wed, 2 Sep 2015 01:14:25 +0300 Subject: [PATCH] Corrected javadoc/xdoc for IllegalTypeCheck --- .../tools/checkstyle/checks/coding/IllegalTypeCheck.java | 8 +++----- src/xdocs/config_coding.xml | 7 ++----- 2 files changed, 5 insertions(+), 10 deletions(-) diff --git a/src/main/java/com/puppycrawl/tools/checkstyle/checks/coding/IllegalTypeCheck.java b/src/main/java/com/puppycrawl/tools/checkstyle/checks/coding/IllegalTypeCheck.java index bfa36532b..27e8f43c6 100644 --- a/src/main/java/com/puppycrawl/tools/checkstyle/checks/coding/IllegalTypeCheck.java +++ b/src/main/java/com/puppycrawl/tools/checkstyle/checks/coding/IllegalTypeCheck.java @@ -34,13 +34,10 @@ import com.puppycrawl.tools.checkstyle.utils.TokenUtils; /** * Checks that particular class are never used as types in variable - * declarations, return values or parameters. Includes - * a pattern check that by default disallows abstract classes. + * declarations, return values or parameters. * *

Rationale: - * Helps reduce coupling on concrete classes. In addition abstract - * classes should be thought of a convenience base class - * implementations of interfaces and as such are not types themselves. + * Helps reduce coupling on concrete classes. * *

Check has following properties: * @@ -90,6 +87,7 @@ import com.puppycrawl.tools.checkstyle.utils.TokenUtils; * * @author Simon Harris * @author Aleksey Nesterenko + * @author Andrei Selkin */ public final class IllegalTypeCheck extends AbstractFormatCheck { diff --git a/src/xdocs/config_coding.xml b/src/xdocs/config_coding.xml index ed974eac8..abc4249d3 100644 --- a/src/xdocs/config_coding.xml +++ b/src/xdocs/config_coding.xml @@ -1924,14 +1924,11 @@ if ("something".equals(x))

Checks that particular classes are never used as types in variable - declarations, return values or parameters. Includes a pattern check - that by default disallows abstract classes. + declarations, return values or parameters.

- Rationale: Helps reduce coupling on concrete classes. In addition - abstract classes should be thought of as convenient base class - implementations of interfaces, and as such, are not types themselves. + Rationale: Helps reduce coupling on concrete classes.