Updating formatter to not drop rego.v1 and future.keywords imports for v1
#7224
Conversation
This file contains 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
to maximize compatibility surface across OPA versions. Adding `--drop-v0-imports` flag to `opa fmt` for opting in to dropping redundant v0 imports. Signed-off-by: Johan Fylling <johan.dev@fylling.se>
johanfylling
changed the title
rego.v1 and future.keywords importsrego.v1 and future.keywords imports for v1
✅ Deploy Preview for openpolicyagent ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
anderseknert
approved these changes
Dec 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
to maximize compatibility surface across OPA versions.
Adding
--drop-v0-importsflag toopa fmtfor opting in to dropping redundant v0 imports.