<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:55:52 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-1340] Parser does not emit all events for extension statements</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-1340</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;This was detected during development of &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-1338&quot; title=&quot;Generate ietf-restconf operations leaf statements&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-1338&quot;&gt;&lt;del&gt;YANGTOOLS-1338&lt;/del&gt;&lt;/a&gt;. EffectiveStatementSupport objects registered for the FULL_DECLARATION phase do not see the full lifecycle of their corresponding statement.&lt;/p&gt;

&lt;p&gt;They see onStatementAdded() first and then onFullDefinitionDeclared(), but not onStatementDefinitionDeclared() or any other of the intermediate callbacks.&lt;/p&gt;

&lt;p&gt;This is understandable from how the reactor operates, but it is not documented anywhere and the integration surface does not provide any guidance which would steer implementers &#8211; all they see is their method not invoked.&lt;/p&gt;

&lt;p&gt;We need to document this somewhere at the very least, but should also explore what we can do to at least warn of this caveat, if not actively prevent it from being possible.&lt;/p&gt;</description>
                <environment></environment>
        <key id="34605">YANGTOOLS-1340</key>
            <summary>Parser does not emit all events for extension statements</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="4" iconUrl="https://jira.opendaylight.org/images/icons/priorities/minor.svg">Low</priority>
                        <status id="10003" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Confirmed</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Fri, 1 Oct 2021 11:49:02 +0000</created>
                <updated>Tue, 7 Jun 2022 12:04:35 +0000</updated>
                                                                            <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="69701" author="rovarga" created="Fri, 1 Oct 2021 11:51:15 +0000"  >&lt;p&gt;This is possible because there is no API-level construct which would restrict the methods available to statement support based on its intended phase.&lt;/p&gt;

&lt;p&gt;I am not sure how feasible is it to create such a coupling construct.&lt;/p&gt;</comment>
                    </comments>
                    <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|i03zwf:</customfieldvalue>

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