Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuration profiles #801

Open
anderseknert opened this issue Jun 5, 2024 · 0 comments
Open

Allow configuration profiles #801

anderseknert opened this issue Jun 5, 2024 · 0 comments
Labels

Comments

@anderseknert
Copy link
Member

Sometimes you'll want slightly different configuration depending on context, or eventually, the file type being linted. As an example, you might want to allow print calls while you're hacking away on some policy project, but forbid them in commits. Excessive warnings in the editor can be annoying, and it would be good if we provided a way to help users avoid that while not compromising on quality.

Another scenario is when we allow linting Rego in different contexts than plain .rego files. Some ideas we've had include linting Rego in markdown files or YAML, but also .rq files. These files have different requirements, and some rules may not be applicable in all contexts. In these cases, we should probably switch profile automatically based on the context.

This is just at the idea stage at this point in time, but noting it down for further refinement later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: TODO
Development

No branches or pull requests

1 participant