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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: