You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a rule in Robocop that parses non-local variables and checks if they are written in uppercase. I realized recently (thanks to the MarketSquare/robotframework-robocop#678) that we should exclude nested variables from the check, so that ${VAR${nested}} would not report a rule violation.
The bug
I realized that correct variables are marked with an error by RF Parsing API. For example, this code, run with robot --variable var1:1 test.robot:
*** Variables ***
${var${1}} 1
*** Test Cases ***
My Test
Log To Console ${var${1}}
executes with PASS state.
But when parsing the variable node, I see that there is an error there:
The bug appears in RF 5 and 6. I haven't tested for earlier versions.
Here are some more examples that raise the same error for RF Parsing API:
Context
We have a rule in Robocop that parses non-local variables and checks if they are written in uppercase. I realized recently (thanks to the MarketSquare/robotframework-robocop#678) that we should exclude nested variables from the check, so that
${VAR${nested}}
would not report a rule violation.The bug
I realized that correct variables are marked with an error by RF Parsing API. For example, this code, run with
robot --variable var1:1 test.robot
:executes with PASS state.
But when parsing the variable node, I see that there is an error there:
The bug appears in RF 5 and 6. I haven't tested for earlier versions.
Here are some more examples that raise the same error for RF Parsing API:
The text was updated successfully, but these errors were encountered: