Medium Description
We are currently exposing SchemaContext, which forces users to deal with SchemaNodes. In order to get migration to EffectiveStatements going we should expose EffectiveModelContext instead, so users can choose which API to use.
Attachments
Issue Links
- is blocked by
-
CONTROLLER-1903 Remove deprecated MD-SAL APIs
-
- Resolved
-
- relates to
-
-
- Resolved
-
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 84796,2 | Add EffectiveModelContextListener | master | yangtools | Status: MERGED | +2 | +1 |
| 84797,5 | Make DOMSchemaService operate of EffectiveModelContext | master | mdsal | Status: MERGED | +2 | +1 |
| 84798,3 | Expose EffectiveModelContext from YangTextSchemaContextResolver | master | yangtools | Status: MERGED | +2 | +1 |
| 84814,3 | Expose EffectiveModelContext from YangParserTestUtils | master | yangtools | Status: MERGED | +2 | +1 |
| 84815,4 | Make DataTree take EffectiveModelContext | master | yangtools | Status: MERGED | +2 | +1 |
| 84816,2 | Switch BasicCodeGenerator to use EffectiveModelContext | master | yangtools | Status: MERGED | +2 | +1 |
| 84859,1 | Expose EffectiveModuleContext from ModuleInfoBackedContext | master | mdsal | Status: MERGED | +2 | +1 |
| 89293,2 | Adjust DOMMountPoint to be EffectiveModelContextProvider | master | mdsal | Status: MERGED | +2 | +1 |
| 89294,5 | Update BindingRuntime{Context,Generator,Types} | master | mdsal | Status: MERGED | +2 | +1 |
| 89397,2 | Allow DOMMountPoint to not have a model context | master | mdsal | Status: MERGED | +2 | +1 |