[YANGTOOLS-943] Invert automatic lifecycle implementation Created: 30/Jan/19 Updated: 15/Mar/19 |
|
| Status: | Confirmed |
| Project: | yangtools |
| Component/s: | data-impl |
| Affects Version/s: | None |
| Fix Version/s: | None |
| 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: |
|
||||||||
| Epic Link: | unlabeled-YANGTOOLS-940 | ||||||||
| Description |
|
With yangtools-2.1.0, the balance of lifecycle between the various node types has shifted. These days most nodes have automatic lifecycle, with presence containers and map entries being the only ones that require different treatment. Invert the logic in SchemaAwareApplyOperation, so that automatic lifecycle becomes the default, and have the two outliers have a mixin which enforces presence. |