Removed experimental flag from multiple rules #3037
Merged
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
Remove experimental tag from avoid-implicit, ignore-errors, key-order, no-free-form, no-prompting, risky-file-permissions, run-once, schema and var-naming. This means that occurrences of these violations will be marked as errors instead of warnings. Users still have the option to add them to their own warn_list or skip_list. All mentioned rules were in place for some time and that is a confirmation that we find their implementation mature.
ssbarnea
requested review from
audgirka,
priyamsahoo,
shatakshiiii,
cidrblock and
ganeshrn
audgirka
approved these changes
Feb 15, 2023
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.
Remove experimental tag from avoid-implicit, ignore-errors, key-order, no-free-form, no-prompting, risky-file-permissions, run-once, schema and var-naming.
This means that occurrences of these violations will be marked as errors instead of warnings. Users still have the option to add them to their own warn_list or skip_list.
All mentioned rules were in place for some time and that is a confirmation that we find their implementation mature.
If you were using the
--strictmode, this change will have no impact.