Context is functional testing.
- User A creates a blueprint “Base” (from now on BPB)
- User A pushes this change to the version control system
- User B creates a blueprint “Derived” (from now on BPD) which inherits from BPB.
- User B pushes this change to the version control system
- User A creates in BPB a “Bind Event to On Test Finished” node, which is linked to a custom event named
“Event Finish Test”
- At the same time User B creates in BPD a “Bind Event to On Test Finished” node, which is linked to a custom event
named “Event Finish Test”
- Both users push their changes to the version control system
As a result: BPD will have 2 Custom Events with the same name, bound to the same “On Test Finished” callback. This is an issue since when the “On Test Finshed” is called, only one of the Custom Event will be triggered.
Known workaround: recreate the Custom Event in BPD and give it a different name from the BPB one (the editor will help in this procedure and gives an error when trying to reuse the same name).
Expected behaviour: when opening BPD I would have expected a “data validation” on all present nodes and an error on the Custom Event with the same name as BPB’s one.
Is this a known bug, or did I miss something?