Releases: robotcodedev/robotcode
v0.13.3
- Highlight localized robot files (RobotFramework >= 5.1)
v0.13.2
- Support for robotidy 3.0
- References are now collected at source code analyze phase
- this speeds up thinks like find references/renaming/highlight and so on
v0.13.1
- Switching to LSP Client 8.0.0 requires a VSCode version >= 1.67
- Create snippets for embedded argument keywords
v0.13.0
- Some corrections in highlightning to provide better bracket matching in arguments
v0.12.1
- Implement API Changes for RobotTidy >= 2.2
- fixes #55
- Switch to new LSP Protocol Version 3.17 and vscode-languageclient 8.0.0
- Disable 4SpacesTab if GitHub CoPilot is showing inline suggestions
- Thanks: @Snooz82
v0.12.0
Hello there,
RobotCode version 0.12.0 is available
Here are the highlights:
- 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:
- Renaming of keywords, variables, tags
- References for arguments also finds named arguments
- see VSCode Documentation
- Test Templates argument analysis
- Basic usage
- Templates with embedded arguments
- Templates with FOR loops and IF/ELSE structures
- see also Robot Framework documentation
- Rework loading and handling source documents
- this speedups a lot of things like:
- UI response
- loading of resources
- 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:
- Reference CodeLenses
- Code lenses are displayed above the keyword definitions showing the usage of the keyword
- You can enable/disable this with the new setting
robotcode.analysis.referencesCodeLens
- Information about possible circular imports
- if one resource file imports another resource file and vice versa an information message is shown in source code and problems list
- Correct handling of keyword only arguments
- 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.
-
- Fix the occurrence of spontaneous deadlocks
- 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
Install RobotCode directly in VSCode or download it from VSCode Marketplace
Also available at Open VSX
Enjoy it!!
Daniel
v0.11.17
added
- Information about possible circular imports
- if one resource file imports another resource file and vice versa an information message is shown in source code and problems list
- References for arguments also finds named arguments
v0.11.12
added
- Reference CodeLenses
- Code lenses are displayed above the keyword definitions showing the usage of the keyword
- You can enable/disable this with the new setting
robotcode.analysis.referencesCodeLens
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