nabl-props crashes when called on a project without properties
If a project has NaBL rules but no properties defined, any call to nabl-props will crash instead of failing if there are no properties set.
An example is a default editor-properties code, that generates the following trace:
Internal error evaluating editor-properties (InterpreterException; see error log)
Submitted by Augusto on 20 March 2014 at 15:31
rewriting failed, trace:
editor_properties_0_0
get_editor_properties_1_2
get_all_editor_properties_1_2
nabl_props_0_0
report_with_failure_0_1
report_failure_0_2
SRTS_EXT_fatal_err_0_2`
Issue Log
On 20 March 2014 at 18:44 Daco Harkes commented:
This was fixed in the runtime libraries: https://github.com/metaborg/runtime-libraries/pull/8
But the runtime libraries aren’t updated yet.
On 20 March 2014 at 19:56 Guido Wachsmuth commented:
You need to poke Gabriël to get the generator updated as well.
On 21 March 2014 at 14:07 Gabriël Konat commented:
I updated the runtime libraries
On 21 March 2014 at 14:07 Gabriël Konat closed this issue.
Log in to post comments