lizzcondrey
commented
5 months ago This is covered in the proper repository under https://github.com/DevOps-MBSE/aac-puml/issues/7, closing this out.
Closed lizzcondrey closed 5 months ago
lizzcondrey
commented
5 months ago This is covered in the proper repository under https://github.com/DevOps-MBSE/aac-puml/issues/7, closing this out.
Reference Issues
714
773
774
775
776
777
778
779
780
781
Summary
As we migrate to the new 0.4.0 baseline, there are tasks on the flip side that need to be completed. 0.4.0 includes refactoring out certain portions of the code base to new repositories. We need to be sure that those portions do get migrated to their new homes making use of the new 0.4.0 system. So, once we have re-baselined we will need to sort the work to re-implement the refactored out functionality.
As an AaC Developer, I want to refactor current AaC gen-puml plugin, so that I provide a useful AaC tool for end users leveraging the updated API.
DoD:
Basic Example
All pertinent PUML plugin pieces need refactored out to their new repository and updated to use the 4.0 API.
What are the drawbacks/impacts of your feature request?
Loss of the PUML functionality until the supporting pieces of the PUML plugin and capability have been migrated over to their new home.
Unresolved questions
No response