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-85 mdsal <p>Restrictions returned for a particular ConcreteType should match the underlying type. The parser generates restrictions in whatever the default is, for example 0 for Short is expressed as a Long. This is largely fine in binding-independent world, but makes it unusable if we want to actually use restrictions with objects of that type.</p> <p>BaseYangTypes is a prime offender, as its singleRangeRestrictions() callers do the wrong thing. Furthermore BindingGeneratorUtil needs to translate whatever it sees to the appropriate type.</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-85

Binding Model API: restrictions do not match java type

Bug Confirmed Unresolved Unassigned Robert Varga pt Wed, 27 May 2015 20:30:33 +0000 Fri, 19 Jan 2024 14:54:28 +0000 14.0.0 Binding runtime 0 3 <p>In mdsal-10.0.0 Restrictions are a final class with a few static factory methods, hence we should be able to isolate the contracts further.</p> <p>Most notably <a href="https://jira.opendaylight.org/browse/MDSAL-736" title="Improve Decimal64 validity checks" class="issue-link" data-issue-key="MDSAL-736">MDSAL-736</a> requires us to also capture fraction-digits in the Restrictions object (or its specialization, really)</p> Blocks MDSAL-736 Development External issue ID 3399 External issue URL Issue Type Rank 0|i02w7z: