Move use of EffectiveStmtCtx.caerbannog() 41/93941/3
authorRobert Varga <robert.varga@pantheon.tech>
Thu, 26 Nov 2020 22:59:55 +0000 (23:59 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Fri, 27 Nov 2020 00:11:30 +0000 (01:11 +0100)
commit31ba731c16033c9fdabbf00fac1ff8adf6d5a6d0
tree5c79f428dc62bbcb7d52f00c6b0aa56322e5ef62
parentf271abeab81db4ae7808d5824b16dcf289023fc1
Move use of EffectiveStmtCtx.caerbannog()

Is it turns out a lot of our logic can be migrated to plain
EffectiveStmtCtx.Current access, reducing the number of warnings
and potential exposure of StatementContextBase internals.

JIRA: YANGTOOLS-1186
Change-Id: Ic5dd688c75a0d0e2285b4bef9f1c77f059d09c1c
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/AbstractEffectiveModule.java
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/EffectiveStmtUtils.java
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/action/ActionStatementSupport.java
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/container/AbstractContainerStatementSupport.java
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/list/AbstractListEffectiveStatement.java
yang/yang-parser-rfc7950/src/main/java/org/opendaylight/yangtools/yang/parser/rfc7950/stmt/notification/NotificationStatementRFC7950Support.java
yang/yang-parser-spi/src/main/java/org/opendaylight/yangtools/yang/parser/spi/meta/StmtContextUtils.java