[YANGTOOLS-1305] Add YangError replacements Created: 14/Jul/21 Updated: 14/Jul/21 Resolved: 14/Jul/21 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | data-api |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.4 |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | Usable RpcError | ||||||||||||
| Description |
|
yang.common.YangError is a nice first approximation to what we need to communicate, but unfortunately it is not enough as it needs a tie-in to yang-data-api. Introduce YangNetconfError as an interface similar to YangError and YangNetconfErrorAware, which allows using errors as attachements to exceptions. Deprecate YangError, so we have clear direction of evolution and there is no ambiguitiy as to which interfaces are preferred. |