Mark StmtContextUtils.isInExtensionBody() FIXME

[yangtools.git] / parser / yang-parser-spi / src / main / java / org / opendaylight / yangtools / yang / parser / spi / meta / StmtContextUtils.java

diff --git a/parser/yang-parser-spi/src/main/java/org/opendaylight/yangtools/yang/parser/spi/meta/StmtContextUtils.java b/parser/yang-parser-spi/src/main/java/org/opendaylight/yangtools/yang/parser/spi/meta/StmtContextUtils.java
index b2eec96a17efb97dbd4aa4347c77bfd9b3544deb..b2b47ad8db369bee2e300232724ae50769a1d66c 100644 (file)
--- a/parser/yang-parser-spi/src/main/java/org/opendaylight/yangtools/yang/parser/spi/meta/StmtContextUtils.java
+++ b/parser/yang-parser-spi/src/main/java/org/opendaylight/yangtools/yang/parser/spi/meta/StmtContextUtils.java
@@ -180,6 +180,15 @@ public final class StmtContextUtils {
         return null;
     }
 
+    // FIXME: 8.0.0: This method goes back as far as YANGTOOLS-365, when we were build EffectiveStatements for
+    //               unsupported YANG extensions. We are not doing that anymore, do we still need this method? Also, it
+    //               is only used in augment support to disable mechanics on unknown nodes.
+    //
+    //               It would seem we can move this method to AbstractAugmentStatementSupport at the very least, but
+    //               also: augments are defined to operate on schema tree nodes, hence even if we have an
+    //               UnknownStatement, but its EffectiveStatement projection supports SchemaTreeAwareEffectiveStatement
+    //               we should operate normally -- the StatementSupport exposing such semantics is responsible for
+    //               arranging the backend details.
     public static boolean isInExtensionBody(final StmtContext<?, ?, ?> stmtCtx) {
         StmtContext<?, ?, ?> current = stmtCtx;