<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:56:03 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[YANGTOOLS-1403] Integrate EffectiveAugmentationSchema into AugmentationSchemaNode/AugmentEffectiveStatement}</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-1403</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;As part of initial NormalizedNode integration and then when we fixed &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1176&quot; title=&quot;Restconf deserialization of xpath for instance identifiers fails to handle &amp;quot;/&amp;quot; in string literals&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1176&quot;&gt;&lt;del&gt;CONTROLLER-1176&lt;/del&gt;&lt;/a&gt;, we have noted an omission on yang.model.api projection.&lt;/p&gt;

&lt;p&gt;The problem is that AugmentationSchemaNode.getChildren() reflects its child statements as declared in source, without taking into account further augmentations at target instantiation site.&lt;/p&gt;

&lt;p&gt;We have solved this with &lt;a href=&quot;https://git.opendaylight.org/gerrit/c/yangtools/+/5594/23/yang/yang-data-impl/src/main/java/org/opendaylight/yangtools/yang/data/impl/schema/transform/base/AugmentationSchemaProxy.java&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;AugmentationSchemaProxy&lt;/a&gt; and then supplanted it with &lt;a href=&quot;https://git.opendaylight.org/gerrit/c/yangtools/+/15900/8/yang/yang-model-util/src/main/java/org/opendaylight/yangtools/yang/model/util/EffectiveAugmentationSchema.java&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;EffectiveAugmentationSchema&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The differences are rather under-documented and at its core demonstrates there is a significant &apos;point of view&apos; difference as to what it &apos;effective children&apos; means:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;in binding, we need to see how augment children were effectively declared&lt;/li&gt;
	&lt;li&gt;in yang.model.api, we would like to project them as replicas of how those statements look at instantiation site&lt;/li&gt;
	&lt;li&gt;in yang.data.api we care about the former due to AugmentationNode, which is a leak (through the datastore operations logic) from binding and we aim to remove this with &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-568&quot; title=&quot;Remove AugmentationIdentifier and AugmentationNode&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-568&quot;&gt;&lt;del&gt;YANGTOOLS-568&lt;/del&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Introduce an additional methods to expose the equivalent of EffectiveAugmentationSchema from both AugmentationSchemaNode and AugmentEffectiveStatement&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
&lt;span class=&quot;code-keyword&quot;&gt;interface&lt;/span&gt; AugmentEffectiveStatement {
  &lt;span class=&quot;code-comment&quot;&gt;// schema/data tree children reflect getDeclared().declaredSubstatements()
&lt;/span&gt;  @NonNull AugmentEffectiveStatement withDeclaredSchemaTree();

  &lt;span class=&quot;code-comment&quot;&gt;// schema/data tree children reflect their augmentations at target site
&lt;/span&gt;  @NonNull AugmentEffectiveStatement withTargetSchemaTree();
}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;which will allow users to flip between the two views.&lt;/p&gt;</description>
                <environment></environment>
        <key id="35307">YANGTOOLS-1403</key>
            <summary>Integrate EffectiveAugmentationSchema into AugmentationSchemaNode/AugmentEffectiveStatement}</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Tue, 1 Mar 2022 19:00:19 +0000</created>
                <updated>Wed, 21 Jun 2023 01:16:19 +0000</updated>
                            <resolved>Wed, 21 Jun 2023 01:16:19 +0000</resolved>
                                                    <fixVersion>11.0.0</fixVersion>
                                    <component>data-util</component>
                    <component>model-api</component>
                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="72311" author="rovarga" created="Wed, 21 Jun 2023 01:16:19 +0000"  >&lt;p&gt;With AugmentationNode gone from yang-data-api, there is very little incentive to actually provide this view, as there really are no more users left. EffectiveAugmentationSchema ends up being deprecated for removal.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="34662">MDSAL-696</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22988">YANGTOOLS-568</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="35216">YANGTOOLS-1404</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i041p3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>