Update syntax of json configuration feature

[namsonx]

Hello Thomas,

 I created this small change for the corner case below during implementing selftest:   
${preprocessor}['definitions']['preproStructure'][${params}['glo']['globalStructure']['general']]: 0.92

 For now both cases below are working:
       - "${preprocessor}['definitions']['preproStructure'][${params}['glo']['globalStructure']['general']]": 0.92
       - ${preprocessor}['definitions']['preproStructure'][${params}['glo']['globalStructure']['general']]: 0.92

Thank you,
Son

[HolQue]

Hello Son,
thank you very much for this clarification! Yesterday I stumbled about this. But when it completely doesn't matter if we put dollar operator statements on the left side of the colon in quotes or not, we should give a strict recommendation to all users about which style to follow. And we should make sure to do it consequently also in all documents we provide.

What shall be the recommendation? With or without quotes?

I will explain this topic later in the test suites tutorial.

[namsonx]

Hello Holger,

 To align with what we improved for the right side of the colon, I personally recommend that we should not use quotes for the left side of the colon also.
 But for now, both ways (with or without quotes in the right side of colon) are acceptable, the reason behind is I don't want the current users of ROBFW-AIO have to rework on their json configuration files :)

Thank you,
Son

[HolQue]

Hello Son,
I agree to your recommendation.

[HolQue]

Hello Son,

only to verify that I have understood the feature now:

There is no syntactical difference between
${params}['global']['param'] : 123
and
"${params}['global']['param']" : 123
In both cases param is of type int.

"param1" : 123
"param2" : "123"
param1 is of type int; param2 is of type str.

"param4" : ${params}['global']['param1']
"param5" : ${params}['global']['param2']
param4 is of type int; param5 is of type str.

"param6" : "${params}['global']['param1']"
param6 is of type str!

"param7" : "${params}['global']['param2']"
param7 is of type str. The quotes around ${params}['global']['param2'] do not matter because param2 is already of type str.

Is this correct?

[namsonx]

Hello Son,

only to verify that I have understood the feature now:

There is no syntactical difference between

${params}['global']['param'] : 123
and
"${params}['global']['param']" : 123
In both cases param is of type int.

"param1" : 123

"param2" : "123"
param1 is of type int; param2 is of type str.

"param4" : ${params}['global']['param1']

"param5" : ${params}['global']['param2']
param4 is of type int; param5 is of type str.

"param6" : "${params}['global']['param1']"

param6 is of type str!
"param7" : "${params}['global']['param2']" param7 is of type str. The quotes around ${params}['global']['param2'] do not matter because param2 is already of type str.

Is this correct?

Hi Holger,

Yes, it is correct!

Thank you,
Son

[HolQue]

You made my day! ;-)

[test-fullautomation]

Hi Son,
looks good to me!
Thank you,
Thomas