[YANGTOOLS-1119] Provide bridge methods from DocumentedNode to EffectiveStatement Created: 03/Jul/20 Updated: 05/Oct/20 Resolved: 05/Oct/20 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | parser |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0 |
| 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 | ||
| Epic Link: | Remove DocumentedNode |
| Description |
|
Most of DocumentedNode subclasses have an equivalent EffectiveStatement. This is certainly true on the implementation side, where the same objects are implementing both aspects. In order to allow users to migrate to EffectiveStatement world, we need to provide a bridge method, allowing to jump from, say, Module to ModuleEffectiveStatement: interface Module { /** * * @throws UnsupportedOperationException */ @NonNull ModuleEffectiveStatement asEffectiveStatement(); } |