Daniel Biehl

@RKhadela143 just add a variables section to your file where you define the ${ELEMENT} variable with a default value, like this: ```robot *** Variables *** ${ELEMENT} ${None} # TEST scope...

Sorry for the late answer, had some busy weeks... Yes this is a bug and I will try to fix it. At the moment I would say, dont use Spaces...

ok, after some investigation, this is a little bit tricky, arguments from keywords in documentation and tags are not resolved by robotframework, here are only global or suite variables allowed....

The documentation for this is currently still in progress and not yet fully accessible to the public. I mainly make the language server for VSCode. I have sporadically tried the...

I've played around a bit with neovim and nvim-lspconfig and have created a working configuration file. Maybe you're interested?

I use the Python method `pathlib.Path.resolve` in some places to get a normalized file name. Depending on how the command line parameters are, I sometimes have absolute paths or relative...

> Tests discovered - repo name is 'doubled' > >  In contrast to RFLS, RobotCode uses RobotFramework algorithms to recognize which suites/test cases/tasks are in the project. Therefore, the...

Thanks for submitting this enhancement. I'll have a look at it after RoboCon...

this could have something to to with #253

Your example is running for me, but you define a variable with a simple type. For complex types the evaluation is not possible at the moment, see #174 and #125...