Skip to content

Improve extraction of runArgs.inputGeneratorFile from jO

Spyros Argyropoulos requested to merge runargs into master

Changes introduced

  • Instead of checking for the presence of runArgs.inputGeneratorFile we execute the jO to see if runArgs.inputGeneratorFile gets assigned a valid value or if it is None

Tests

jO submitted in !637 (merged)

PASSES

Using runArgs.inputGeneratorFile = "a"

ERROR

Using #runArgs.inputGeneratorFile = "a" (commented string)

PASSES

Using runArgs.inputGeneratorFile = a (where a is an undefined value in the jO)

PASSES

Using runArgs.inputGeneratorFile = a,b (where a,b are two strings previously defined in the jO)

For instance in the jO I put:

a="a"
b="b"
runArgs.inputGeneratorFile = a,b

ERROR

Issues resolved

Closes #120 (closed)

Merge request reports