Version 0.4.0 #137
Merged
Version 0.4.0 #137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
**New Features** - Updated to latest version of Trieste - Uses Trieste's YAML and JSON parsers and emitters - Uses Trieste's more robust Unicode support - Passes broken up into a `Reader`, which parses Rego files, and a `Rewriter` which performs unification - Added the `encoding` and `graphs` builtins - Added `set_log_level_from_string` and `setLogLevelFromString` to make it easier to set the log level. All executables now use this option. **Improvements** - The Interpreter caches intermediate versions of all modules, reducing query execution time - All of the early passes have been rewritten and are more efficient, resulting in reduced parsing time - The reduction of the input passes (and their restriction to a single file) along with other optimizations to header files has resulted in reduced compile times - The `rego_fuzzer` xecutable allows for more fine-grained fuzzing and testing of the Rego toolchain - Multiple bug fixes **Deprecation** - The `regoSetInputJSON` method is a misnomer, as the input does not strictly need to be JSON. This has been replaced with an (otherwise identical) function called `regoSetInputTerm` which does the same thing, and the `JSON` version has been deprecated. **Breaking Changes** - The `rego_trieste` executable has been replaced by the new `rego_fuzzer` executable **New Test Coverage** - `base64builtins` - `base64urlbuiltins` - `hexbuiltins` - `jsonbuiltins` - `reachable` - `urlbuiltins` Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
matajoh
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Features
Reader, which parses Rego files, and aRewriterwhich performs unificationencodingandgraphsbuiltinsset_log_level_from_stringandsetLogLevelFromStringto make it easier to set the log level. All executables now use this option.Improvements
rego_fuzzerexecutable allows for more fine-grained fuzzing and testing of the Rego toolchainDeprecation
regoSetInputJSONmethod is a misnomer, as the input does not strictly need to be JSON. This has been replaced with an (otherwise identical) function calledregoSetInputTermwhich does the same thing, and theJSONversion has been deprecated.Breaking Changes
rego_triesteexecutable has been replaced by the newrego_fuzzerexecutableNew Test Coverage
base64builtinsbase64urlbuiltinshexbuiltinsjsonbuiltinsreachableurlbuiltinsFixes #112
Fixes #114
Fixes #115
Fixes #116
Fixes #124
Fixes #126
Fixes #127
Fixes #129
Fixes #130
Fixes #134
Fixes #135