<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:55:01 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-1042] ModuleEffectiveStatement fails to index statements from submodules</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-1042</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;Our implementation for ModuleEffectiveStatement indexes effective statements in the StmtContext before considering submodules, simply because the context is passed to AbstractSchemaEffectiveDocumentedNode without these statements.&lt;/p&gt;

&lt;p&gt;This is then worked around by AbstractEffectiveModule constructor, which manually attaches these modules before indexing them (for SchemaNode-only indexes).&lt;/p&gt;

&lt;p&gt;Code structure here seems to be very difficult and hacky, which points towards the fact the code needs to be restructured.&lt;/p&gt;</description>
                <environment></environment>
        <key id="32221">YANGTOOLS-1042</key>
            <summary>ModuleEffectiveStatement fails to index statements from submodules</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <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="-1">Unassigned</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Mon, 25 Nov 2019 15:41:06 +0000</created>
                <updated>Wed, 27 Nov 2019 09:17:31 +0000</updated>
                            <resolved>Wed, 27 Nov 2019 09:17:31 +0000</resolved>
                                                    <fixVersion>4.0.3</fixVersion>
                    <fixVersion>3.0.7</fixVersion>
                                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="67457" author="rovarga" created="Mon, 25 Nov 2019 16:08:02 +0000"  >&lt;p&gt;It looks as though either &apos;include&apos; or &apos;belongs-to&apos; statements should really end up inlining the definitions once the submodule has been completely defined. From these two the &apos;include&apos; statement looks like a better fit, as it is already used in this capacity for linkage resolution.&lt;/p&gt;

&lt;p&gt;A slight wrinkle here is that submodules may have recursive includes, which really are not instructions to inline the particular submodule but rather reference it. To resolve this, I think the overall behaviour of &apos;include&apos; needs to be different based on whether it is used in a submodule or a module.&lt;/p&gt;

&lt;p&gt;This way all effective statements for a particular module should be resolved in StmtContext before EffectiveModuleStatement is instantiated, resolving this issue.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="32219">YANGTOOLS-1040</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="32220">YANGTOOLS-1041</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="32224">YANGTOOLS-1044</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|i03q67:</customfieldvalue>

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