[YANGTOOLS-415] Java Binding: generated Key classes should enforce leaf presence Created: 05/Mar/15 Updated: 10/Apr/22 Resolved: 18/Mar/15 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| Description |
|
RFC6020 forces leaves which are part of a key to be present. While that can change somewhere down the road, the Key classes should enforce presence of arguments as appropriate by performing a null check in the constructor. |
| Comments |
| Comment by Robert Varga [ 18/Mar/15 ] |
|
Key statement make leaves mandatory, so this should be solved as part of BUG-2797. |