[YANGTOOLS-1307] Correctly tag missing key violations Created: 14/Jul/21 Updated: 18/Jan/24 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | data-api, data-util |
| Affects Version/s: | None |
| Fix Version/s: | 14.0.0, 13.0.2 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
RFC6020 section 8.3.1 provides guidance as to what error-tag should be reported when we are missing a key leaf in a list during parsing:
If all keys of a list entry are not present, the server MUST reply
with a "missing-element" error-tag in the rpc-error.
Add the appropriate exception and YangNetconfError awareness so that it may be decoded by users. |