Flow to xml inconsistencies

[Daan0709]

• Receivers now no longer generate forwards
• exits persist their attributes

Closes #425, Closes #393

[Matthbo]

You now specifically check if an element is a receiver and only add forwards if its not. I was wondering if the Forwards are seen as child elements, if so you should check on that instead to determine when to add Forwards

[Daan0709]

You now specifically check if an element is a receiver and only add forwards if its not. I was wondering if the Forwards are seen as child elements, if so you should check on that instead to determine when to add Forwards

At this point forwards are not yet child elements, instead they are represented by all the edges that are within a flow. Since the receiver is the only element in here that can have an edge on the flow but can not have a forward in the xml, this seemed like the easiest solution.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud