regal
regal copied to clipboard
Regal is a linter for Rego, with the goal of making your Rego magnificent!
Regal should be able to lint [rq](https://git.sr.ht/~charles/rq) files "out of the box", meaning that if: - A user runs `regal lint script.rq`, we should recognize it as Rego with rq...
I don't think it's a goal we're touting anywhere, but given the overarching goals of the project it should go without saying that if we can do something either in...
One thing that would be interesting (and potentially useful) is if Regal included some optional rules to check the directory structure of a policy repo, and reported on things that...
We will need to figure out what **ignoring** something means in the context of aggregate rules. ```yaml rules: testing: some-aggregate-rule: level: error ignore: files: - foo/bar.rego ``` The way we...
It should be as simple to create aggregate rules as other rules using the Regal scaffolding commands. We should add an `--aggregate` flag to `regal new rule`, that would add...
Some configuration options to the `ignore` attribute that would be nice additions: ```yaml ignore: # both of these would be true by default dot-git-dir: true use-git-ignore: true files: - foo.rego...
Currently, Regal will parse any `*.rego` file which isn't excluded by an ignore-filter. While this is a reasonable default behavior, it should be possible to tell Regal what a "Rego...
We're doing a lot of wrapping around errors in Regal, and I think that's good for providing context and trace capabilities. It however leads to some error messages being printed...
It should be possible to say that all rules of function matching a pattern, like "does not start with _", should have a metadata annotation.
It would be useful to have a linter rule that checked the most common places where some form of credentials are normally used, and make at least some effort to...