package org.opendaylight.yangtools.yang.data.api.schema.tree;
/**
- * Enumeration of all possible node modification states. These are used in
- * data tree modification context to quickly assess what sort of modification
- * the node is undergoing.
+ * Enumeration of all possible node modification states. These are used in data tree modification context to quickly
+ * assess what sort of modification the node is undergoing.
*/
public enum ModificationType {
/**
* This node has appeared because it is implied by one of its children. This type is usually produced when a
* structural container is created to host some leaf entries. It does not have an associated before-image.
*
+ * <p>
* Its semantics is a combination of SUBTREE_MODIFIED and WRITE, depending on which context it is being interpreted.
*
+ * <p>
* Users who track the value of the node can treat it as a WRITE. Users transforming a {@link DataTreeCandidate} to
* operations on a {@link DataTreeModification} should interpret it as a SUBTREE_MODIFIED and examine its children.
* This is needed to correctly deal with concurrent operations on the nodes children, as issuing a write on the
* This node has disappeared because it is no longer implied by any children. This type is usually produced when a
* structural container is removed because it has become empty. It does not have an associated after-image.
*
- * Its semantics is a combination of SUBTREE_MODIFIED and DELETE, depending on which context it is being interpreted.
- * Users who track the value of the node can treat it as a DELETE, as the container has disappeared. Users
- * transforming a {@link DataTreeCandidate} to operations on a {@link DataTreeModification} should interpret it as
- * a SUBTREE_MODIFIED and examine its children.
+ * <p>
+ * Its semantics is a combination of SUBTREE_MODIFIED and DELETE, depending on which context it is being
+ * interpreted. Users who track the value of the node can treat it as a DELETE, as the container has disappeared.
+ * Users transforming a {@link DataTreeCandidate} to operations on a {@link DataTreeModification} should interpret
+ * it as a SUBTREE_MODIFIED and examine its children.
*
+ * <p>
* This is needed to correctly deal with concurrent operations on the nodes children, as issuing a delete on the
* DataTreeModification would end up removing any leaves which have not been present at the DataTree which emitted
* this event.