Remove duplicate RequireOneLineDocComment rule
#319
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
greg0ire
approved these changes
Apr 27, 2023
ostrolucky
approved these changes
Apr 27, 2023
SenseException
approved these changes
Apr 27, 2023
|
Thanks @tomudding ! |
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.
I have removed the first occurrence of the
SlevomatCodingStandard.Commenting.RequireOneLineDocCommentrule as it was most recently changed (in #294, from what I can tell to catch more instances of one-line doc comments, however, as we see now the new rule was already introduced in #252). The second occurrence also appears to fit better with the surrounding rules.This fixes #318.