Releases: robotcodedev/robotcode
Releases · robotcodedev/robotcode
v0.11.11
added
- Project wide code analysis
- there are some new settings that allow to display project-wide problems:
robotcode.analysis.diagnosticMode
Analysis mode for diagnostics.openFilesOnly
Analyzes and reports problems only on open files.workspace
Analyzes and reports problems on all files in the workspace.- default:
openFilesOnly
robotcode.analysis.progressMode
Progress mode for diagnostics.simple
Show only simple progress messages.detailed
Show detailed progress messages. Displays the filenames that are currently being analyzed.- default:
simple
robotcode.analysis.maxProjectFileCount
Specifies the maximum number of files for which diagnostics are reported for the whole project/workspace folder. Specifies 0 or less to disable the limit completely.- default:
1000
- default:
robotcode.workspace.excludePatterns
Specifies glob patterns for excluding files and folders from analysing by the language server.
- there are some new settings that allow to display project-wide problems:
- Rework loading and handling source documents
- this speedups a lot of things like:
- UI response
- finding references
- renaming of keywords and variables
- loading reloading libraries and resources
- When you create/rename/delete files, keywords, variables, you get an immediate response in the UI
- this speedups a lot of things like:
v0.11.10
- renaming of keywords and variables
- speedup loading of resources
v0.11.9
added
- Return values of keywords calls can be assigned to variables in the debugger console
-
You can call keywords in the debugger console just as you would write your keyword calls in robot files.
Everything that starts with'! '
(beware the space) is handled like a keyword call, for example:! Log Hello
would call the keyword
Log
and writesHello
to report.! Evaluate 1+2
calls
Evaluate
and writes the result to the log.To assign the result of a keyword to a variable write something like
! ${result} Evaluate 1+2
This will assign the result of the expression to the variable
${result}
in the current execution context.A more complex example:
! ${a} @{c}= ${b} Evaluate "Hello World!!! How do you do?".split(' ')
A side effect of this is that the keyword calls are logged in log.html when you continue your debug session.
-
v0.11.8
added
- Test Templates argument analysis
- Basic usage
- Templates with embedded arguments
- Templates with FOR loops and IF/ELSE structures
- see also Robot Framework documentation
v0.11.7
added
- optimize restart language clients if configuration changed
- support for progress feature of language server protocol
- correct WHILE snippets
- handle invalid regular expressions in embedded keywords
- correct handling of templates with embedded arguments
v0.11.6
- none so far
v0.10.2
- Implement Selection Range support for Robot Framework
- starting from a point in the source code you can select the surrounding keyword, block (IF/WHILE,...), test case, test section and so on
- Provide better error messages if python and robot environment not matches RobotCode requirements
- fixes #40
- Correct restart of language server client if python interpreter changed
- Correct start of root test item if
robotcode.robot.paths
is used - Correct find references at token ends
- If the cursor is at the end of a keyword, for example, the keyword will also be highlighted and the references will be found.
- Correct error in find variable references with invalid variables in variable section
- Correct find references at token ends
- If the cursor is at the end of a keyword, for example, the keyword will also be highlighted and the references will be found.
v0.11.3
- Fix selection range on white space
v0.11.2
- Implement Selection Range support for Robot Framework
- starting from a point in the source code you can select the surrounding keyword, block (IF/WHILE,...), test case, test section and so on