Parameter inside dictionary not resolved

[HolQue]

JSON input:

{
   "val01" : "string",
   "val02" : 123,
   "val03" : "${val01}",
   "val04" : ["A", "B", "C"],
   "val05" : {"A" : "${val01}", "B" : "${val02}", "C" : "${val03}"},
   "val06" : true,
   "val07" : false,
   "val08" : null
}

JsonPreprocessor output:

{'val01': 'string',
 'val02': 123,
 'val03': 'string',
 'val04': ['A', 'B', 'C'],
 'val05': {'A': 'string', 'B': 123, 'C': '${val01}'},
 'val06': True,
 'val07': False,
 'val08': None}

The value of val05.C is '${val01}', even in case of the value of val03 is already 'string'.

Expected: The value of val05.C is 'string'.

[test-fullautomation]

Hi Son,
please look into this.
Expectation is what Holger writes.
Thank you,
Thomas

[namsonx]

Hello Holger, Hello Thomas,

This scenario is similar with the scenario Holger mentioned in issue #80 that a nested parameter is used to other nested parameter.
In this case, the parameter val03 is defined with nested param "${val01}", then "${val03}" is used as nested param in val05.

My concern again is: Dose this scenario occurs in reality?

Thank you,
Son

[test-fullautomation]

Hi Son,
yes, the preprocessor must resolve this properly, too. Any scenario is possible.
Parameters must be resolved according to their definition order recursively.
Thank you,
Thomas

[namsonx]

Hello Holger, Hello Thomas,

This issue was fixed with in commit e6851712 on the stabi branch (namsonx/task/stabi_branch)

Thank you,
Son

[HolQue]

Retest successful

[test-fullautomation]

solved and already merged #147