-
Notifications
You must be signed in to change notification settings - Fork 24
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
Enforce code style more strictly #1747
Comments
For typehint annotations we could use: |
I think we should take into account that the typehints could be needed by external libraries (i.e. doctrine) (bstrooband - Oct 15, 2019) |
|
Experimented with Slevomat CS rules. I added these rules to the phpcs.xml
That resulted in a nice set of required changes in the Bottom line is: in order to use PHP 7 type hints on the existing code. We should update the existing code to use type hints correctly. (Michiel Kodde - Oct 21, 2019) |
Created a branch that addresses some of the tasks of this story The todo on this branch is to implement PHP 7 strict types and type definitions on all classes. This is a change that should not be taken lightly. As increasing the strictness of the application might lead to unexpected errors/issues. (Michiel Kodde - Oct 21, 2019) |
This issue is imported from pivotal - Originaly created at Oct 15, 2019 by Michiel Kodde
The last couple of PR reviews, we had some discussion about enforcing thecode style. See some tasks below.
The text was updated successfully, but these errors were encountered: