Skip to content

Comment and metadata rules #188

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

Merged
merged 2 commits into from
Jun 29, 2023
Merged

Comment and metadata rules #188

merged 2 commits into from
Jun 29, 2023

Conversation

anderseknert
Copy link
Member

  • Add no-whitespace-comment rule in the style category, because comments should start with a whitespace!
  • Add invalid-metadata-attribute rule in the bugs category. This one checks that all attributes of a metadata block are valid, i.e. not custom outside of the custom map.

Comments should start with a whitespace!

Co-authored-by: Stephan Renatus <[email protected]>
Signed-off-by: Anders Eknert <[email protected]>
This one checks that all attributes of a metadata block are
valid, i.e. not custom outside of the custom map.

Signed-off-by: Anders Eknert <[email protected]>
"entrypoint",
"custom",
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could become a bit of a hassle if OPA introduces further attributes. But OK for now.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True. Not sure if there's a way to enumerate them from the Go API, but that would be preferable 🤔

@anderseknert anderseknert merged commit 2f68245 into main Jun 29, 2023
@anderseknert anderseknert deleted the metadata branch June 29, 2023 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants