From 20c8e54c5fd31fd8694bde78cce53ca47671b87c Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Sat, 20 Dec 2014 10:31:11 +0100 Subject: [PATCH] Revert dea1ca9855 Actually collection types are not harmonized to their interface counterpart; this was implemented in the first proposal but wasn't applied in the final review. See gh-2206 --- .../main/asciidoc/appendix-configuration-metadata.adoc | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/appendix-configuration-metadata.adoc b/spring-boot-docs/src/main/asciidoc/appendix-configuration-metadata.adoc index bef5495654..f3774b8dc8 100644 --- a/spring-boot-docs/src/main/asciidoc/appendix-configuration-metadata.adoc +++ b/spring-boot-docs/src/main/asciidoc/appendix-configuration-metadata.adoc @@ -121,12 +121,9 @@ The JSON object contained in the `properties` array can contain the following at | The class name of the data type of the property. For example, `java.lang.String`. This attribute can be used to guide the user as to the types of values that they can enter. For consistency, the type of a primitive is specified using its wrapper counterpart, - i.e. `boolean` becomes `java.lang.Boolean`. Collection types are harmonized to their - interface counterpart and define the actual generic types, i.e. - `java.util.HashMap` becomes - `java.util.Map`. Note that this class may be a - complex type that gets converted from a String as values are bound. May be omitted if - the type is not known. + i.e. `boolean` becomes `java.lang.Boolean`. Note that this class may be a complex type + that gets converted from a String as values are bound. May be omitted if the type is + not known. |`description` | String