<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:55:30 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-1214] Reuse effective substatements along entire copy axis</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-1214</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;In the following model:&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;
module foo {
  namespace foo;
  prefix foo;

  grouping grp {
    container foo;
  }

  container bar {
    uses grp;
  }

  container baz {
    uses grp;
  }
}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;We end up with distinct objects for bar/foo and baz/foo. Disregarding SchemaPath, this is because the effectiveConfig property changes separately and the instantiation of baz/foo does not see the object at bar/foo (and vice-versa).&lt;/p&gt;

&lt;p&gt;In order to make this work we need to instantiate a statement-specific lookup table in grp/foo&apos;s ReactorStmtCtx. When instantiating bar/foo, this would be populated with an effective key, i.e. effectiveConfig + history (+ whatever) and pointing to bar/foo. When instantiating baz/foo, the bar/foo instance would be recognized as the equivalent and reused.&lt;/p&gt;</description>
                <environment></environment>
        <key id="33757">YANGTOOLS-1214</key>
            <summary>Reuse effective substatements along entire copy axis</summary>
                <type id="10102" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10316&amp;avatarType=issuetype">Sub-task</type>
                            <parent id="32327">YANGTOOLS-1067</parent>
                                    <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</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="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Tue, 26 Jan 2021 10:26:46 +0000</created>
                <updated>Sat, 4 Dec 2021 14:11:17 +0000</updated>
                            <resolved>Sat, 4 Dec 2021 14:11:17 +0000</resolved>
                                                    <fixVersion>8.0.0</fixVersion>
                                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="68948" author="rovarga" created="Mon, 1 Feb 2021 18:12:24 +0000"  >&lt;p&gt;An example of how this is important can be seen here:&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;image-wrap&quot; style=&quot;&quot;&gt;&lt;img src=&quot;https://jira.opendaylight.org/secure/attachment/16008/16008_image-2021-02-01-19-10-01-822.png&quot; height=&quot;648&quot; width=&quot;1165&quot; style=&quot;border: 0px solid black&quot; /&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;the two expanded objects are the same, but due to &apos;flags&apos; and &apos;original&apos; (and their effects of substatements) being different from the original, these are instantiated separately.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="16008" name="image-2021-02-01-19-10-01-822.png" size="553412" author="rovarga" created="Mon, 1 Feb 2021 18:10:04 +0000"/>
                    </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|i03wvb:</customfieldvalue>

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