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.
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
Support configuration using pyproject.toml #16
Support configuration using pyproject.toml #16
Changes from 23 commits
7736f7f
376c6bc
c769daa
0d278bf
92398fc
1ab1c9e
651fd53
3622da3
58b15b4
a465a29
933207d
dc58c5a
e62836d
4603f43
edc2766
566b561
1abff4f
7abc430
8cadd1a
862da7f
06e0957
da190b7
12d49fc
ae091fe
99c4da3
a50d027
52080c0
923d020
4af4971
87998db
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be named
config
(also inRule.params
->Rule.config
)?Reason is, I find it confusing to have these 2 concepts, which are fundamentally the same but named differently
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this actually prevents confusion because these things are not the same IMO. Yes both are to configure a
Rule
, but one configuration is input for a method whereas the other also does other things (update severity). I am open to change it, maybe @druzhinin-kirill has an opinion on what is less confusing?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rule.config_params 😄
No strong opinion, however, I would prefer avoiding key mismatch variable names:
so either variable is
params
, or the argument isrules
(only if it's achievable for zero cost, super minor anyway).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the user point of view, this is all "rule config", right?
Now internally the config is divided in two,
severity
andparams
/config
. I don't think it's an issue, we could do something likewhich I believe is self explanatory, and doesn't require the use of multiple terms? WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the user point of view it's indeed all the same, it's internals only.
Ok I will go for using
config
insideRuleConfig
👌