https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/MDSAL-385 mdsal <p>This is vaguely related to something I had originally raised 2 years ago on <a href="https://lists.opendaylight.org/pipermail/yangtools-dev/2016-July/001508.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/yangtools-dev/2016-July/001508.html</a> &amp; Co. including <a href="https://wiki.opendaylight.org/view/YANG_Tools:Design:Binding_Specification_v2_Analysis#Other_ideas_for_improving_the_v2_Binding_Spec" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/YANG_Tools:Design:Binding_Specification_v2_Analysis#Other_ideas_for_improving_the_v2_Binding_Spec</a> but I cannot find an issue for this, so here it is ...</p> <p><a href="https://jira.opendaylight.org/browse/MDSAL-18" title="Return an empty list and never null from list-valued parameters in generated models" class="issue-link" data-issue-key="MDSAL-18"><del>MDSAL-18</del></a> does something about null safe collection fields in gen. code. What does this mean for the respective Builders? Can we make those easier and more null safe to use now?</p> MDSAL-385

YANG Data Object Builders for non-null lists

Improvement Medium Resolved Won't Do Unassigned Michael Vorburger Fri, 9 Nov 2018 09:51:47 +0000 Sat, 16 Mar 2019 16:37:22 +0000 Sat, 16 Mar 2019 16:37:22 +0000 0 2 <p>Can you re-phrase the description to state the explicit ask?</p> <p>What exactly is the code change you are proposing?</p> <p>What are its benefits (in what use cases)?</p> <p>Missing specification. Please reopen with clarifications.</p> Development Rank 0|i03ka7: