Simplify spacing requirements for rego format - #6730
Open
evankanderson wants to merge 1 commit into
Open
Conversation
|
coverage: 61.772% (-0.006%) from 61.778% — evankanderson:easier-rego-metadata into mindersec:main |
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
2 participants
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.
Summary
Currently,
mindev test(particularly on Windows) is very picky about rego format files. (It requires at least one space even on blank comment lines.) Handle windows newlines in body correctly and accept completely-empty comment lines (which otherwise break multi-paragraph guidance and other text blocks).Testing
Tested manually while converting rules to Rego using the pattern:
# METADATAcommentapiVersion,type,name,def.eval.rego.def, etc)