[YANGTOOLS-1143] Sort out yang.model.repo.{api,spi,util} placement Created: 18/Oct/20 Updated: 10/Apr/22 Resolved: 13/Feb/21 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0 |
| Type: | Task | Priority: | High |
| 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: | Integrate completely with JMPS |
| Description |
|
During the course of transitioning to JPMS modules the repo.api package placement came up. Resolve it somehow – either by creating a new component, or renaming it. This needs to be examined with yang-parser-api in mind. |
| Comments |
| Comment by Robert Varga [ 11/Feb/21 ] |
|
These classes are really a different take on yang-parser-api, where the management of models follows transformations and keeps all sorts of caches. The interfaces could be hosted in yang-parser-api, but that might cause confusion. These need to be split into yang-repo-{api,spi) hosting repo.api, repo.spi. Current contents of repo.util should go to repo.spi. Finally the yang-parser-rfc7950 bits need to be examined and cleaned up as well. |