[MDSAL-48] Binding Specification: Type empty needs better representation than Boolean or Null vs NonNull Created: 15/Sep/14  Updated: 20/Mar/19  Resolved: 20/Mar/19

Status: Resolved
Project: mdsal
Component/s: Binding codegen, Binding runtime
Affects Version/s: None
Fix Version/s: 4.0.0

Type: Improvement
Reporter: Tony Tkacik Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows
Platform: PC


Issue Links:
Blocks
is blocked by MDSAL-237 Milestone: Implement Binding Specific... Resolved

 Description   

In Binding specification v1 YANG type empty was represented as Boolean, which was bit confusing. In normalized Node it is represented as java.lang.Void type which is bit unusual type to work with in normal code path.

Type empty needs better representation which will clearly describe it semantics:
Leaf present. The best way is to introduce enumeration with value PRESENT
eg. Empty.PRESENT and null could still be not present.



 Comments   
Comment by Tony Tkacik [ 01/Mar/16 ]

Type Empty is introduced here:

https://git.opendaylight.org/gerrit/#/c/31897/4

Generated at Wed Feb 07 20:08:30 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.