Community
Participate
Working Groups
Created attachment 132492 [details] Fix Consider the following mwe file 'bar.mwe' in project A: <workflow> <component file="com/sample/foo.mwe"> <propDefined value="zonk" /> <propNotDefined value="zonk" /> </component> </workflow> and this file 'com/sample/foo.mwe' in project B: <workflow> <property name='bla' value='${propDefined}'/> <property name='bla' value='${missingProp}'/> </workflow> The editor will not resolve the reference to foo.mwe. Any assignement (propDefined, propNotDefined) will be highlightes as an error. However, the workflow will run fine. Please find a fix for the unresolved file attached. It contains a workaround that suppresses the error markers on the assignments, too. Expected behaviour: propDefined is not highlighted as an error, propNotDefined is highlighted as an error. Furthermore, I'ld expect a warning, that "missingProp" is not defined in 'bar.mwe'.
Patch is applied, thx.
Thanks, Dennis. I'll file a second bug for the issue with property validation.
closing