Releases: mauvaisetroupe/ea-design-it
Releases · mauvaisetroupe/ea-design-it
Release 0.2.9
Release 0.2.8
- Improve import mechanism for capabilities/application mapping files #65
Release 0.2.7
- Attach created Function flow to existing landscape during plantuml import #63
Release 0.2.5
- performance improvement for Applications Plantuml Diagram #62
Release 0.2.3
- Use Spring JPA projection to avoid EAGER loading on entities list pages #62
Release 0.2.2
- Caching is not cluster-safe #40
- Plantuml diagram - escape \n character #58
- Landscape can be considered as a Set of Interfaces using nos alias for Functional Flow. A kind of anonymous Flow is created, one per interface. This fake Flow allows a description over an interface in the context of a landscape #56
- When organizing Flows, step description editable #57
- Export Plantuml description #29
- DrawIO refactoring - multiple interfaces for one Edge
- Import FunctionalFlow as plantuml Sequence Diagram #60
Release 0.2.0
- Upgrade to JHipster 7.6.0
- With new JHipster version, migration from sringfox to springdoc, fixing bug with SortedSet, especially empty landscape creation (#47)
- Add cypress testing (UI testing)
- Landscapes linked to an interface is not display (#50)
- Disable FunctionalFlow delete button when used by a Landscape (#48)
- Disable Interface delete button when used by a Functional Flow (#49)
- When deleting a Landscape, ask for deleting owned Functional Flows (#51)
- When deleting a Functional Flow, ask for deleting owned Interfaces (#52)
- Import an Flow excel file should be idempotent. Add new column in Excel file ('External'). If External=yes, do not create Flow, but attach it to Landscape if exists (#53 )
- FunctionalFlow can be displayed as Sequence Diagram or component diagram (#54)