Skip to content

Releases: open-policy-agent/opa-idea-plugin

v0.3.0

04 Apr 10:32
16fcf24
Compare
Choose a tag to compare

Release notes for v0.3.0

Changes by Kind

Bug or Regression

  • Grammar: allow to use of infix operation as argument of a function. This expression was parsed as an error:

v0.2.0

04 Apr 10:19
e00aa17
Compare
Choose a tag to compare

Release notes for v0.2.0

Changes by Kind

Feature

Documentation

  • Fix typo in the documentation (#54, @lukasz-kaminski)
  • Update instruction du use stable channel when installing opa though Jetbrains market place (#53, @vgramer)

Bug or Regression

  • Grammar: access to function's return value without assigning it to a variable. These expressions were parsed as an error:
    • fun_obj(x) = h { h := {"a": {"b": [x,2]}} }
    • aRule { a = fun_obj(1).a } (#59, @vgramer)

v0.1.0

04 Apr 10:14
693bc9a
Compare
Choose a tag to compare

Release notes for v0.1.0

Changes by Kind

Refactoring

  • Add tests on grammar and validate test files with opa check command (#40, @irodzik)
  • Refactoring of Opa action codes and improve comment (#38, @asadali)

Feature

  • Add the following opa action
  • Add the script to check that versioned source files (*.java; *.kt) contains the license header and call it in github action (#49, @vgramer)
  • Build flavored ide. Some features like creating a rego project is only available on IDEA. This PR allows building the different flavors of the plugin for each ide version. This is transparent for the user (he see only one plugin market place) (#44, @vgramer)
  • Grammar: add % operator and tests for grammar (#39, @irodzik)
  • Implements auto-closing feature (brace, parenthesis and bracket ) (#41, @vgramer)
  • Index TOTO in rego comment (#26, @vgramer)
  • OpaTestRunConfiguration: add the full output of the command to the root node (#52, @vgramer)
  • Support for opa test, test coverage on project workspace and opa check on current open document, shows output in console window (all support for console window showing output is in extensions/OPAActionToolWindow) (#30, @frankiecerk)

Documentation

  • Add opa icon for plugin installation (#36, @vgramer)
  • Add user and tech documentation (#3, @vgramer)
  • Instructions for download plugin from Jetbrains market place (#48, @frankiecerk)

Bug or Regression

  • Fix test run configuration:
    • Don't discriminate test configurations based on the file name:
      • user can eval or test a package in any rego file
      • user can test any rule starting with test_in any rego file
      • user can evaluate any rule not starting with test_ in any rego file
    • Make bundle dir parameter required to create a test configuration => avoid message Testing Framework quit unexpectedly when creating a test configuration from gutter
    • Generated name of the runConfiguration start with the name of the command to easily know which configuration type will be generated (#50, @vgramer)
  • Grammar: fixed string regex
    highlighting for rule heads (#19, @frankiecerk)%