-
Notifications
You must be signed in to change notification settings - Fork 144
[TASK] Add separate methods for RuleSet::removeRule()
, with deprecation
#1249
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
Conversation
171e5ee
to
4467362
Compare
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.
The new method(s) also should get tests.
1c92d96
to
d312040
Compare
Passing `string` or `null` to `removeRule()` is deprecated. The new method handles that functionality. Relates to #1247.
d312040
to
0352420
Compare
RuleSet::removeMatchingRules()
, with deprecationRuleSet::removeRule()
, with deprecation
I was planning to move the existing tests to the new method when the deprecated API was removed. But you're right, they should be added now, and maybe can be more 'unit'. |
For consistency with current nomenclature, `Rule` is used in the test method names, despite that they are now called 'declarations'. (Renaming to match the current spec is a separate project.)
9ed08c9
to
eab3658
Compare
Suggested changes made... |
Note that I changed the PR title and OP message. I was unable to do the same for the OC (original commit) due to subsequent commits. Could you update the final commit message for |
Passing
string
ornull
toremoveRule()
is deprecated. The new methods handle that functionality.Relates to #1247.