anchor.diff:  	]}
   ----
   
  -
  -
  -===== Class reference
  +Note that, in the preceding example, any other value is also allowed.
  +
  +===== Class Reference
   The **class-reference** provider auto-completes classes available in the project. This
  -provider supports these parameters:
  +provider supports the following parameters:
   
   [cols="1,1,2,4"]
   |===
  
positive.code: 	}
  ----
  
  Will produce meta-data information for `server.name`, `server.host.ip` and
  `server.host.port` properties. You can use the `@NestedConfigurationProperty`
  annotation on a field to indicate that a regular (non-inner) class should be treated as
  if it were nested.
  
  TIP: This has no effect on collections and maps as those types are automatically
  identified and a single meta-data property is generated for each of them.
  
  
  [[configuration-metadata-additional-metadata]]
  ==== Adding additional meta-data
  Spring Boot's configuration file handling is quite flexible; and it is often the case
  that properties may exist that are not bound to a `@ConfigurationProperties` bean. You
  may also need to tune some attributes of an existing key. To support such cases and allow
  you to provide custom "hints", the annotation processor will automatically merge items
  from `META-INF/additional-spring-configuration-metadata.json` into the main meta-data
  file.
  
  If you refer to a property that has been detected automatically, the description,
  default value and deprecation information are overridden if specified. If the manual
  property declaration is not identified in the current module, it is added as a brand new
  property.
  
  The format of the `additional-spring-configuration-metadata.json` file is exactly the same
  as the regular `spring-configuration-metadata.json`. The additional properties file is
  optional, if you don't have any additional properties, simply don't add it.
  
negative.code: 
  |`level`
  |String
  |The level of deprecation, which can be either `warning` (the default) or `error`. When a
   property has a `warning` deprecation level, it should still be bound in the environment.
   However, when it has an `error` deprecation level, the property is no longer managed and
   is not bound.
  
  |`reason`
  |String
  |A short description of the reason why the property was deprecated. If no reason is
  available, it may be omitted. It is recommended that descriptions be short paragraphs,
   with the first line providing a concise summary. The last line in the description should
   end with a period (`.`).
  
  |`replacement`
  |String
  |The full name of the property that _replaces_ this deprecated property. If there is no
   replacement for this property, it may be omitted.
  |===
  
  NOTE: Prior to Spring Boot 1.3, a single `deprecated` boolean attribute can be used
  