v0.8.0

added

• Introduce new version scheme to support pre-release versions of the extension
  • see README
• Rework handling VSCode test items to ensure all defined tests can be executed, also when they are ambiguous
  • see #37
• Semantic highlighting of new WHILE and EXCEPT options for RF 5.0
• Support for inline IF for RF 5.0
• Support for new BREAK, CONTINUE, RETURN statements for RF 5.0

v0.7.9

• none so far

v0.7.5

0.7.5

v0.7.4

added

• automate uploading of release assets

v0.7.3

• automate creating github release for a new version tag

v0.7.0

added

• Add dryRun property to launch configuration
• Add "Dry Run" and "Dry Debug" profile to test explorer
  • You can select it via Run/Debug dropdown or Right Click on the "green arrow" before the test case/suite or in test explorer and then "Execute Using Profile"
• Mark using reserved keywords like "Break", "While",... as errors
• Support for NONE in Setup/Teardowns
  • see here
  • fixes #38
• Decrease size of extension package
• Sligtly correct displayName and description of VSCode package, for better relevance in Marketplace search
  • See here #39

v0.6.0

added

• Improved variable analysis

  • In an expression like ${A+'${B+"${F}"}'+'${D}'} ${C}, every single 'inner' variable will be recognized, you can hover over it, it can be found as reference, you can go to the definition, ...
  • Also in python expressions like ${{$a+$b}} variables are recognized
  • Support for variables in expression in IF and WHILE statements
    • in something like $i<5 the variables are recognized
  • Only the name of the variable is used for hovering, goto and ..., not the surrounding ${}

• Support importing variable files as module for RobotFramework 5

• Depending on selected testcase names contains a colon, a semicolon is used as separator of prerunmodifier for executing testcases

  • fixes #20
  • note: i think you should not use colons or semicolon in testcase names ;-)

• Improve Debugger

  • The debugger shows variables as inline values and when hovering, it shows the current variable value not the evaluted expression
  • Variables in the debugger are now resolved correctly and are sorted into Local/Test/Suite and Global variables
  • Fix stepping/halt on breakpoint for IF/ELSE statements if the expression is evaluated as False
  • Rework of stepping and stacktrace in the debugger
    • Only the real steps are displayed in the stack trace

• Optimize keyword matching

  • all keyword references also with embedded arguments + regex are found
  • ambigous embedded keywords are recognized correctly, also with regex
  • speed up finding keyword references
  • fix #28
  • addresses #24

• Ignoring robotcode diagnostics

  • you can put a line comment to disable robotcode diagnostics (i.e errors or warnings) for a single line, like this:

  *** Test cases ***
  first
      unknown keyword  a param   # robotcode: ignore
      Run Keyword If    ${True}
      ...    Log    ${Invalid var        # robotcode: ignore
      ...  ELSE
      ...    Unknown keyword  No  # robotcode: ignore

• Propagate import errors from resources

  • errors like: Resource file with 'Test Cases' section is invalid are shown at import statement
  • Note: Robocop has it's own ignore mechanism

• Initialize logging only of "--log" parameter is set from commandline

  • fixes #30

• Optimize loading of imports and collecting keywords

  • this addresses #24
  • one of the big points here is, beware of namespace pollution ;-)

• Full Support for BDD Style keywords

  • includes hover, goto, highlight, references, ...

v0.5.5

added

• correct semantic highlightning for "run keywords"
  • now also named arguments in inner keywords are highlighted
• correct handling of parameter names in "run keywords" and inner keywords
• correct handling of resource keywords arguments

v0.5.4

added

• Keyword call analysis
  • shows if parameters are missing or too much and so on...
• Highlight of named arguments
• Improve handling of command line variables when resolving variables
• Remove handling of python files to reduce the processor load in certain situations

v0.5.3

added

• Resolving static variables, closes #18

  • RobotCode tries to resolve variables that are definied at variables section, command line variables and builtin variables. This make it possible to import libraries/resources/variables with the correct path and parameters.
    Something like this:

  *** Settings ***
  Resource          ${RESOURCE_DIR}/some_settings.resource
  Library           alibrary    a_param=${LIB_ARG}
  Resource          ${RESOURCE_DIR}/some_keywords.resource

  • If you hover over a variable, you will see, if the variable can be resolved

• show quick pick for debug/run configuration

  • if there is no launch configuration selected and you want to run code with "Start Debugging" or "Run without Debugging", robotcode will show you a simple quick pick, where you can select a predefined configuration

• some cosmetic changes in updating Test Explorer

• correct handling of showing inline values and hover over variables in debugger

• correct handling of variable assignment with an "equal" sign

• add more regression tests