-
-
Notifications
You must be signed in to change notification settings - Fork 590
[WIP] Apply Doctrine CS #968
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
|
*/ | ||
public function dispatch($eventName, string $class, string $format, Event $event): void; | ||
public function dispatch(string $eventName, string $class, string $format, Event $event): void; |
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.
good catch, this is a bug! :)
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.
There is more of missing types, some break more things so I would probably not touch types in first iteration and do them separately, then add proper docblocks for properties etc. (this one is especially in extremely bad shape in Serializer).
Then we can also consider PHPStan.
yes
It's totally useless and very often outdated, Git already provides more accurate information. |
Also please decide the following:
|
How to run the comment to apply the rules? is it documented somewhere? |
Since the project has (would)
|
will try, tnx! |
implemented in #971 |
Initial import of Doctrine CS.
@goetas Excluded some rules you mentioned before that you don't like.
Also excluded BC-breaking rules since the code base is currently a bit messy, a lot of inconsistent/missing parameter/return types. :(
Only applied to src/ to give you some look at the result, and to have something to discuss/improve later on.