User-Story Node with multiple output handles

[Geissemanu]

Related Issues

• Closes #81
• Fixes #

Definition of Done

• [x] User Story
  • [x] All Acceptance Criteria met
• [x] Code
  • [x] No more code needed
  • [x] No known bugs
• [x] Clean Code
  • [x] Comments have been created for new code
  • [x] ESLinter found no issues (editor & executor only)
  • [x] No unavoidable Code Smells
• [x] Testing
  • [x] Existing Tests pass
  • [x] New Unit Tests created
  • [x] New Unit Tests pass
• [x] SonarCloud Quality Gate passed

Definition of more than Done (optional)

• [ ] Testing
  • [ ] New Integration Tests created
  • [ ] New Integration Tests passed

[sonarcloud[bot]]

[API] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[sonarcloud[bot]]

[Executor] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[Geissemanu]

The changes in the Executor will wrap the results of every node in an Object. The Object contains a Field for every outgoingHandle and saves the result there. If in the Future Nodes with diferent Outputs will be created, they can be differenciated by the Outgoing Handle ID.

[sonarcloud[bot]]

[Identity] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[sonarcloud[bot]]

[Editor] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[sonarcloud[bot]]

[Executor] Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication