-
Notifications
You must be signed in to change notification settings - Fork 2
Description
I define a string value as composite string in these ways:
"composite_string_1" : (1.01)--'${string_01}'--(1.02)--'${string_02}'
"composite_string_2" : ${string_01} -- '${string_01}${string_02}' -- ${string_02}
In both cases the quotes around the composite string at the right hand side of the colon are missing. But in case of a composite string (dollar operator expressions together with hard coded string parts) quotes are required. This requirement is not fulfilled. Therefore errors are expected.
The difference between composite_string_1 and composite_string_2 is: The value of composite_string_1 contains dollar operator expressions inside, whereas the value of composite_string_2 starts and ends with a dollar operator expression. It seems that this difference has an (unwanted) impact on the parser.
The error message for composite_string_1 is like expected: Expecting value:
The error message for composite_string_2 deviates: Expecting ',' delimiter
But the root problem is the same in both cases: missing quotes. Therefore no value can be identified. Therefore the error message also for composite_string_2 is expected to be: Expecting value:
Metadata
Metadata
Labels
Projects
Status