Calling an EOperation that doesn't have a returning type causes an internal error during validation?
Expected behavior
Calling an EOperation without a return type is processed as a call to a method returning void.
How to reproduce
Steps to reproduce the behavior:
Create an EClass
Create an EOperation without specifying a return type
Call the operation from ALE
Witness the editor show an error marker
Additional context
ALE version: maybe a branch not yet merged onto master (will edit with details)
It looks like an old AQL bug in EOperationService that has been uncovered recently with the improvements made to ALE's validators (the error is not new but was swallowed before).
Bug description
Calling an EOperation that doesn't have a returning type causes an internal error during validation?
Expected behavior
Calling an EOperation without a return type is processed as a call to a method returning void.
How to reproduce
Steps to reproduce the behavior:
Additional context
It looks like an old AQL bug in EOperationService that has been uncovered recently with the improvements made to ALE's validators (the error is not new but was swallowed before).