anchor.diff:    ///
     ///     // Displaying the depth value would be distracting. Instead only display
     ///     // if the depth value is missing.
  -  ///     description.add(new ObjectFlagProperty<int>('depth', depth, ifNull: 'no depth'));
  +  ///     properties.add(new ObjectFlagProperty<int>('depth', depth, ifNull: 'no depth'));
     ///
     ///     // bool flag that is only shown when the value is true.
  -  ///     description.add(new FlagProperty('using primary controller', value: primary));
  -  ///
  -  ///     description.add(new FlagProperty(
  +  ///     properties.add(new FlagProperty('using primary controller', value: primary));
  +  ///
  +  ///     properties.add(new FlagProperty(
     ///       'isCurrent',
     ///       value: isCurrent,
     ///       ifTrue: 'active',
  
positive.code: /// Property with a [value] of type [T].
  ///
  /// If the default `value.toString()` does not provide an adequate description
  /// of the value, specify [description] defining a custom description.
  ///
  /// The [hidden] property specifies whether the property should be hidden from
  /// the default output (e.g. the output given by [toStringDeep]).
  
negative.code:   ///     // good terse description, write a DiagnosticsProperty subclass as in
    ///     // the case of TransformProperty which displays a nice debugging view
    ///     // of a Matrix4 that represents a transform.
    ///     properties.add(new TransformProperty('transform', transform));
    ///
    ///     // If the value class has a good `toString` method, use
    ///     // DiagnosticsProperty<YourValueType>. Specifying the value type ensures
  