- 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)
- CI: fix release-note and publish pipeline (#169, @vgramer)
- Compatibility with IDEA base ide 2023.2 (#153, @sandhose)
- Add support for IDEA 2023.1 (#144, @SilverSilence)
- CI: update opa to version 0.47.4 (#141, @charlieegan3)
- Add project settings under
Preference -> Languages & Framworks -> Opa
to configureopa check
options. the--strict
options is enable by default (#133, @vgramer) - Add support for IDEA 2022.3 (#139, @vgramer)
- Fix NPE when loading project (#138, @vgramer)
- Grammar: allow trailing comma in function arg list (#132, @vgramer)
- 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)
- Automate release process, create CHANGLOG.md with update the previous releases notes (#99, @vgramer)
- Grammar: rename rules:
- Remove references to old repo
vgramer/opa-idea-plugin
. The repository has been transferred toopen-policy-agent
organization (#83, @vgramer)
- Grammar: allow factor expression (ie parenthesis ). These expressions were passed as an error:
- Grammar: allow complex expression as array index. These expressions were parsed as an error:
- Grammar: allow complex expression for array and object value. these expressions were parsed as an error:
- Grammar: allow empty query in else clause. These expressions were reported as an error
-
Run intellij-plugin-verifier to check plugin binary compatibility in github action
- 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
- Grammar: allow to use of infix operation as argument of a function. This expression was parsed as an error:
- Implements auto-closing feature (brace, parenthesis and bracket ) (#41, @vgramer)
- Improve speed and security of CI Job:
- Cache gradle dependencies between run.
- check the signature of the Gradle wrapper. More info at https://github.com/gradle/wrapper-validation-action (#55, @vgramer)
- Fix typo in the documentation (#54, @lukasz-kaminski)
- Update instruction du use stable channel when installing opa though Jetbrains market place (#53, @vgramer)
- Grammar: access to function's return value without assigning it to a variable. These expressions were parsed as an error:
- Add tests on grammar and validate test files with
opa check
command (#40, @irodzik) - Refactoring of Opa action codes and improve comment (#38, @asadali)
- Add the following opa action
- trace of selected text to code
- check (#37, @frankiecerk)
- 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)
- 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)
- 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)
- Don't discriminate test configurations based on the file name:
- Grammar: fixed string regex highlighting for rule heads (#19, @frankiecerk)