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-453 mdsal <p>Binding list/map treatment should make sure we do not return nulls here, as it imposes additional burden on the user. When a list/map does not exist, we should return an empty immutable list/map, so that things are kept consistent.</p> <p>This automatically means DTOs do not leak mutable maps, no matter what. Even when a map is initialized (empty in this case, but we are generalizing here) to an HashMap in the builder, it is fair for the resulting object to return an immutable implementation (i.e. an empty ImmutableMap).</p> MDSAL-453

Eliminate the diffence between null and empty nodes

Task Medium Resolved Won't Do Robert Varga Robert Varga Tue, 21 May 2019 23:04:23 +0000 Tue, 21 Apr 2020 10:09:03 +0000 Tue, 21 Apr 2020 10:09:03 +0000 Binding codegen Binding runtime 0 1 <p>As part of the epic, we are really going the other way – we are turning empty maps into nulls, as we provide utility methods to treat them as non-null. This will lower the non-leakage guarantees, but will make it easier for users to transition.</p> <p>As noted previously, we are really doing the opposite, allowing the user to use nonnullFoo() or getFoo() to make a choice between empty or nullable collections.</p> Development Epic Link MDSAL-449 Rank 0|i03nyf: