Skip to content

Latest commit

 

History

History
208 lines (133 loc) · 12 KB

CHANGELOG.md

File metadata and controls

208 lines (133 loc) · 12 KB

Release notes for v0.13.0

Changes by Kind

Uncategorized

Release notes for v0.12.0

Changes by Kind

Feature

  • Compatibility for ide 2023.3. (#164, @vgramer)
  • Support for idea 2024.1 Grammar: rules with multidimensional array heads support Grammar: else expressions no longer consider ':=' invalid (#166, @spoage)

Uncategorized

Release notes for v0.11.0

Changes by Kind

Uncategorized

Release notes for v0.10.0

Changes by Kind

Uncategorized

Release notes for v0.9.0

Changes by Kind

Feature

  • Add project settings under Preference -> Languages & Framworks -> Opa to configure opa check options. the --strict options is enable by default (#133, @vgramer)
  • Add support for IDEA 2022.3 (#139, @vgramer)

Bug or Regression

Release notes for v0.8.0

Changes by Kind

Feature

  • Highlight raw string and make color configurable in the color setting page. (#122, @vgramer)
  • Add compatibility for idea based ide version 2022.1 (#129, @vgramer)

Release notes for v0.7.0

Changes by Kind

Feature

Documentation

  • Automate release process, create CHANGLOG.md with update the previous releases notes (#99, @vgramer)

Release notes for v0.6.0

Changes by Kind

Feature

  • Make plugin compatible with platform version 203 and 211 (#101, @asadali)

Release notes for v0.5.0

Changes by Kind

Refactoring

  • Grammar: rename rules:
  • Remove references to old repo vgramer/opa-idea-plugin. The repository has been transferred to open-policy-agent organization (#83, @vgramer)

Bug or Regression

  • Grammar: allow factor expression (ie parenthesis ). These expressions were passed as an error:
    • a4:= (1 - 3) - (2 +5)
    • reverse(l) = [l[j] | _ = l[i]; j := (count(l) - 1) - i] (#92, @vgramer)
  • Grammar: allow complex expression as array index. These expressions were parsed as an error:
    • x:= x[minus(count(x),1)]
    • index_last(l, x) = t[minus(count(t), 1)] { #something} else = -1 { # something}
    • rule1{ x:= x[count(x) - 1)] } (#91, @vgramer)
  • Grammar: allow complex expression for array and object value. these expressions were parsed as an error:
    • arr7 := [1 + 2 - 4, count(arr6) / abs(arr5[0])
    • a6 := { a: 1 > 2, b: { c: object.get(a2, a, default) + abs(c) - 2 }} (#90, @vgramer)
  • Grammar: allow empty query in else clause. These expressions were reported as an error
    • foo = true { input.x < input.y } else = false
    • foo = true { false } else = { true } (#85, @vgramer)

Release notes for v0.4.0

Changes by Kind

Feature

  • Implement auto closing quote feature (#69, @vgramer)

  • Run intellij-plugin-verifier to check plugin binary compatibility in github action

    1. update org.jetbrains.intellij Gradle plugin because the new version offers a task to run the plugin verifier. Consequently, remove the ideaDependencyCachePathcustomization which is not needed anymore.
    2. add a job to run plugin verifier (#62, @vgramer)

Bug or Regression

  • Fix tests for github action and macOS Big Sur (#73, @vgramer)
  • Grammar: allow import between rules and complex expression in else statement (#80, @vgramer)
  • Grammar: don't allow multi-line in strings (#67, @vgramer)
  • Grammar: fix rule-head and expr-infix
    • a:= 1 + 2 was parsed as an error
    • assignment was valid inside affectation (eg a := b = 1 + 2) but should not.
    • a := 1 + 2 +3 was parsed as an error (#74, @vgramer)

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:

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)

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)