Skip to content

[ 2374916 ] Additional bracket harms the parameter scope detection #403

@HolQue

Description

@HolQue

Within a composite data structure I overwrite the value of an existing parameter "D" in this way:

${params}[1]['B'][0]['D'] : 11

This works like expected.

Now I make an error. I add an opening curly bracket after '{params}':

${params}{[1]['B'][0]['D'] : 11

The error message is:

'Missing scope for parameter '${D}'. To change the value of this parameter, an absolute path must be used: '${params}[1]['B'][0]['D']' or '${params.1.B.0.D}'.'

Of course, the expression on the left hand side of the colon is invalid now. But the error message is much far away from reality.

Intuitively I would expect a syntax error. A detailed statement like a missing scope cannot be given in this case, because such a
statement would require a valid syntax of the expression.

Do we have any valid case where a parameter (${params}) can be followed by an opened curly bracket? I don't think so.

Please try to rework the error handling in such cases.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions