You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #1230, we added support for the reuse of a prepared query when linting for rego and aggregate rules. It'd be nice to be able to bring similar gains to the server's Eval Code Lens function too.
Currently, the current project must be parsed and compiled before being evaluated, there are two parts to this.
reloading the new bundle ready for evaluation in the background
Updating the logic to use the same prepared query for many evaluation runs. Perhaps evaluating the whole bundle, but then selecting only the rule in question after evaluation.
Considerations, can we have a prepared query that evaluates the rule based on the input rather than evaluating more than we need to? (/sending http.send calls etc.)
The text was updated successfully, but these errors were encountered:
In #1230, we added support for the reuse of a prepared query when linting for rego and aggregate rules. It'd be nice to be able to bring similar gains to the server's Eval Code Lens function too.
Currently, the current project must be parsed and compiled before being evaluated, there are two parts to this.
Considerations, can we have a prepared query that evaluates the rule based on the input rather than evaluating more than we need to? (/sending http.send calls etc.)
The text was updated successfully, but these errors were encountered: