1. Introducing static code analysis
into our project has made code
reviews more efficient
Noël
NOV 27, 2020
@English Night vol.5
presented by GAOGAO Inc.
2. Introduction
<?php
/** ellipsis */
class Noel extends BackEnd implements Engineer
{
use Laravel, AWSCloudFormation;
public function performCodeReviews(): object
{/** ellipsis */}
public function focusOnNodeJSInPrivate(): void
{/** ellipsis */}
}
7. Whenever I was working on
the code review on Github
there would be
a bunch of conflicts due to subtle
differences, which include
- indent size differences in the same line
- single quote or double quote
- the differences with the number of whitespaces
8. How much time can we spare
fixing these nonsense differences ?
More than 10 file
conflicts per PR..!?
Come on !!!!!
9. We want to focus on thinking about
whether the architecture, the algorithm,
and the naming
are optimized or not.
More than 10 file
conflicts per PR..!?
Come on !!!!!
17. Larastan
As for every tool except Larastan,
the parts used Facade and Magick Methods
automatically cause errors even if they
don’t have any problems on Laravel App.
Reasons why we had chosen
these two packages
18. Reasons why we had chosen
these two packages
Let us care for dependency managers by
simply only using composer and not using
npm or yarn for PHP environment.
PHP-CS-Fixer
22. Benefits Larastan
・Putting more emphasis on
writing phpdoc than before
・Becoming conscious of the type of
arguments, return values,
(Making up for the lack of PHP)