feat(ui): Add drag-and-drop support for importing integration XMLs as flow diagrams #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
In addition to current support for dropping exported Flow JSON files, the Canvas can now accept dropped integration XML files. This makes it easier to keep Flow diagrams in-sync with executable XML logic, enabling faster iteration and up-to-date documentation for routes.
Details
The critical logic is contained in the
eipFlowToDiagram.ts, which converts theEipFlowresponse to a format compatible with the app's store. Note, this feature depends on #29, so the flow-translator service must be available for the XML file import to function.High-level steps:
toFlowendpointEipFlowresponse is transformed and imported into the app's state storeChecklist
npm run precommitfrom theuidirectory)