-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.0 - New Assignments and Behavior Name Change #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as with the 3. PR. Please re-run the build action of this PR once more after the previous PRs have been merged, just to be sure.
.filter(flow -> flow.getDestinationNode().equals(node)) | ||
.filter(flow -> flow.getEntityName().equals("")).toList(); | ||
|
||
String controlFlowName = "" + CONTROL_FLOW_NAME; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didnt you do this code in a previous PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, to run some tests i also copied it over to this branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTMN
Added handling for new Assignments to Web2DFD and DFD2Web Converter
Adjusted Web2DFD and DFD2Web Converter to new Assignment semantic
Adjusted Behavior Naming where necessary
New tests for new Assignments
!!Forth Merge of 4.0 - Do DataFlowAnalysis first!!