SlevomatCodingStandard.Classes.ClassStructure: Group for __invoke method#1683
Closed
freerich wants to merge 1 commit intoslevomat:masterfrom
Closed
SlevomatCodingStandard.Classes.ClassStructure: Group for __invoke method#1683freerich wants to merge 1 commit intoslevomat:masterfrom
SlevomatCodingStandard.Classes.ClassStructure: Group for __invoke method#1683freerich wants to merge 1 commit intoslevomat:masterfrom
Conversation
Contributor
|
Thanks I've implemented it here: ad01519 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As mentioned in issue #1471, we need to give special treatment to __invoke methods. In some applications, __invoke methods are as important as __construct methods, such as in EventHandler, CommandHandler, and invokable controllers.
Adding this specific “invoke” case might be much easier than handling individual method names, as discussed in issue #1098.