Interface and Description |
---|
de.danielbechler.diff.access.ExclusionAware
This was a shortcut to extract the "exclude" flag from the ObjectDiffProperty annotation. Since we found
a better way to do that, it is not needed anymore and will be removed in future versions.
|
Class and Description |
---|
de.danielbechler.diff.path.NodePathValueHolder
The ConfigNode provides a much more powerful way to store values for NodePaths.
|
Method and Description |
---|
de.danielbechler.diff.selector.CollectionItemElementSelector.getItem()
Low-level API. Don't use in production code. May be removed
in future versions.
|
de.danielbechler.diff.selector.MapKeyElementSelector.getKey()
Low-level API. Don't use in production code. May be removed in future versions.
|
de.danielbechler.diff.node.CategoryFilteringVisitor.includeOnly(String)
This method is confusing. The name implies only nodes with the given category
will be included, but that's not the case. Instead every previously included category will
also be included. On top of that every excluded category will remain excluded. This method
will be removed in future versions until the feature is explicitly requested.
|
de.danielbechler.diff.node.DiffNode.isExcluded()
This method was a shortcut to extract the "exclude" flag from the ObjectDiffProperty
annotation. Since we found a better way to do that, it is not needed anymore and will be removed in future
versions. The name is also misleading. It implies that here lies the truth about the exclusion, but only the
InclusionService can tell for sure. This flag is just only little piece of the puzzle.
|
de.danielbechler.diff.access.ExclusionAware.isExcludedByAnnotation() |
Annotation Type Element and Description |
---|
de.danielbechler.diff.introspection.ObjectDiffProperty.excluded
Please use ObjectDiffProperty.inclusion() instead. When used in conjunction with ObjectDiffProperty.inclusion(), the latter one will win over ObjectDiffProperty.excluded().
|