Update: Uniform messages for the rules in "complexity" section #11759
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.
What is the purpose of this pull request? (put an "X" next to item)
What rule do you want to change?
It is proposed to unify the content of messages from the category "complexity". And make them more informative.
Does this change cause the rule to produce more or fewer warnings?
no changed
How will the change be implemented? (New option, new default behavior, etc.)?
exports.meta.messages
data
in acontext.report
method callPlease provide some example code that this change will affect:
rules config
What does the rule currently do for this code?
What will the rule do after it's changed?
What changes did you make? (Give an overview)
complexity, max-depth
max-len, max-classes-per-file
max-lines, max-lines-per-function
Is there anything you'd like reviewers to focus on?
Also I want to change the messages for the rules: max-classes-per-file, max-statements-per-line, and possibly other similar rules that use numeric metrics. Are there any other such rules?