Expose EffectiveModelContext from DOMSchemaService
Description
is blocked by
relates to
Activity
Show:
Robert Varga September 30, 2019 at 8:26 PM
Controller's DOMSchemaService is derived from our DOMSchemaService and we cannot use default methods (due to aries bug), hence we cannot make this transition in a reasonable way.
Punt until controller is purged (Aluminium MRI).
Robert Varga August 19, 2019 at 3:52 PM
It is also interesting note that NMDA is really dictating datastore-centricity, i.e. each datastore has its own SchemaContext (encapsulated in DatastoreContext in Yang Tools). This may mean that DOMSchemaService is either a more complicated beast or does not exist.
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.