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
    • robotcode.workspace.excludePatterns Specifies glob patterns for excluding files and folders from analysing by the language server.
• 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
• 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 writes Hello 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
    • robotcode.workspace.excludePatterns Specifies glob patterns for excluding files and folders from analysing by the language server.
• 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

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 writes Hello 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.