feat(docs): fetch docs from monorepository branches #70
innocenzicoding-conventions.yml
on: pull_request
Run style check
18s
Annotations
2 errors, 10 warnings, and 2 notices
|
Run style check
Process completed with exit code 1.
|
|
maintainability/too-many-properties:
src/Web/Blog/BlogPost.php#L10
Class has too many properties.
Having a large number of properties can make classes harder to understand and maintain.
Help: Try reducing the number of properties, or consider grouping related properties into a single object.
|
|
best-practices/literal-named-argument:
src/Web/Homepage/HomeController.php#L26
Literal argument `'.md'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: '.md')` instead of `function_name('.md')`.
|
|
best-practices/literal-named-argument:
src/Web/Homepage/HomeController.php#L22
Literal argument `'/'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: '/')` instead of `function_name('/')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L40
Literal argument `'ellison'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: 'ellison')` instead of `function_name('ellison')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L40
Literal argument `'Hello World'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: 'Hello World')` instead of `function_name('Hello World')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L40
Literal argument `'ellison'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: 'ellison')` instead of `function_name('ellison')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L35
Literal argument `'/ellison/preview'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: '/ellison/preview')` instead of `function_name('/ellison/preview')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L32
Literal argument `'ellison'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: 'ellison')` instead of `function_name('ellison')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L30
Literal argument `'ellison'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: 'ellison')` instead of `function_name('ellison')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L27
Literal argument `'/ellison'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: '/ellison')` instead of `function_name('/ellison')`.
|
|
best-practices/literal-named-argument:
src/Web/Code/EllisonController.php#L21
Literal argument `'/ellison'` should be passed as a named argument for clarity.
Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value.
Help: Consider changing the call to `function_name(literal: '/ellison')` instead of `function_name('/ellison')`.
|
|
best-practices/no-unused-parameter:
src/Web/Analytics/StatsController.php#L47
Parameter `$b` is never used.
This parameter is declared but not used within the arrow function.
Help: Consider prefixing the parameter with an underscore (`_`) to indicate that it is intentionally unused, or remove it if it is not needed.
|
|
best-practices/no-unused-parameter:
src/Web/Analytics/StatsController.php#L19
Parameter `$clock` is never used.
This parameter is declared but not used within the method.
Help: Consider prefixing the parameter with an underscore (`_`) to indicate that it is intentionally unused, or remove it if it is not needed.
|