<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:29 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-848] No methods isAugmenting and isAddedByUses available on ActionDefinition</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-848</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;An action can be added in an augment or a grouping, like a DataSchemaNode.&#160;&#160;&lt;/p&gt;

&lt;p&gt;But there are no methods isAugmenting and isAddedByUses available on ActionDefinition, like there is on DataSchemaNode.&#160;&#160; This is an omission in the API.&lt;/p&gt;

&lt;p&gt;The same would be applicable for NotificationDefinition.&lt;/p&gt;</description>
                <environment></environment>
        <key id="29231">YANGTOOLS-848</key>
            <summary>No methods isAugmenting and isAddedByUses available on ActionDefinition</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="verthezpw">Peter Verthez</reporter>
                        <labels>
                    </labels>
                <created>Fri, 16 Feb 2018 11:30:00 +0000</created>
                <updated>Thu, 22 Feb 2018 08:05:30 +0000</updated>
                            <resolved>Tue, 20 Feb 2018 10:03:31 +0000</resolved>
                                                                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="61100" author="rovarga" created="Mon, 19 Feb 2018 12:07:04 +0000"  >&lt;p&gt;Both these methods are marked as deprecated, as they are a leak from declared to effective model. As such they are only used by MDSAL&apos;s binding generator, which does not handle actions nor non-root notifications, as far as I can tell. What exactly is the use case for them?&lt;/p&gt;</comment>
                            <comment id="61101" author="verthezpw" created="Mon, 19 Feb 2018 12:29:25 +0000"  >&lt;p&gt;We have a converter from YANG to YIN (loosely based on YinExportUtils in ODL, but since that was not complete at that time we wrote our own).&#160;&#160; That needs to know whether an action is added by augmentation or uses, to be able to regenerate the content of a module properly.&lt;/p&gt;</comment>
                            <comment id="61120" author="rovarga" created="Tue, 20 Feb 2018 10:03:13 +0000"  >&lt;p&gt;Proper implementation of YIN module export does not actually require any of this. If your implementation requires those bits, they can be derived given the whole-Module visibility, hence I suggest you do that in your implementation, as introducing these methods:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;goes directly against the direction we want to take&lt;/li&gt;
	&lt;li&gt;introduces more coupling in yang parser&lt;/li&gt;
	&lt;li&gt;adds maintenance burden&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="61121" author="verthezpw" created="Tue, 20 Feb 2018 10:10:21 +0000"  >&lt;p&gt;Can you clarify then how we can derive that?&lt;/p&gt;</comment>
                            <comment id="61166" author="rovarga" created="Thu, 22 Feb 2018 08:05:30 +0000"  >&lt;p&gt;For example: isAugmenting() means that either the node has a different namespace (i.e. augment from another module) or there is a corresponding augment statement in current module. isAddedByUses() is similar.&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|i03ahj:</customfieldvalue>

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