Conversation
**New Features** - Updated the supported version of Rego to v0.65.0. - `json.marshal_with_options` - `numbers.range_step` - `rego.v1` import and behaviour, plus a set of tests in `regov1.yaml` - The interpreter now returns more than one `Result` when appropriate, and separates out the `Bindings` and `Terms`. - The output of `rego` is now JSON instead of plain text - Added `regoOutputSize`, `regoExpressions`, `regoBindingsAtIndex`, and `regoExpressionsAtIndex` to the C API - Updated the Python and Rust wrappers to use the new API **Breaking Changes** - Output of `rego` tool has changed. Any downstream tooling that was parsing that will need to be updated to parse the JSON. - `rego::wf_result` has changed. Any tooling that was using the output node directly will need to be updated - the `add_*` methods on `Interpreter`, as they now perform parsing, now produce either a `nullptr` if successful or an error `Node`. Downstream consumers that were checking the boolean return value will need to be updated. Behavior in the C API is unchanged, but there will now be detailed parse/compile errors when an individual module etc. fails to compile. Signed-off-by: Matthew Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
Signed-off-by: Matthew A Johnson <matjoh@microsoft.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
json.marshal_with_optionsnumbers.range_steprego.v1import and behaviour, plus a set of tests inregov1.yamlResultwhen appropriate, and separates out theBindingsandTerms.regois now JSON instead of plain textregoOutputSize,regoExpressions,regoBindingsAtIndex, andregoExpressionsAtIndexto the C APIBreaking Changes
regotool has changed. Any downstream tooling that was parsing that will need to be updated to parse the JSON.rego::wf_resulthas changed. Any tooling that was using the output node directly will need to be updatedadd_*methods onInterpreter, as they now perform parsing, now produce either anullptrif successful or an errorNode. Downstream consumers that were checking the boolean return value will need to be updated. Behavior in the C API is unchanged, but there will now be detailed parse/compile errors when an individual module etc. fails to compile.Closes #140
Closes #145
Fixes #109
Fixes #110
Fixes #111
Fixes #117
Fixes #121