feat(docs): fetch docs from monorepository branches #71
innocenzicoding-conventions.yml
on: pull_request
Run style check
28s
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/Highlight/Injections/EmphasizeInjection.php#L23
Literal argument `'%s%s%s'` 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: '%s%s%s')` instead of `function_name('%s%s%s')`.
|
|
best-practices/literal-named-argument:
src/Highlight/IsTagInjection.php#L29
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/Highlight/Injections/H1Injection.php#L26
Literal argument `'</span>'` 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: '</span>')` instead of `function_name('</span>')`.
|
|
best-practices/literal-named-argument:
src/Highlight/Injections/H1Injection.php#L24
Literal argument `'<span class="hl-console-h1">'` 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: '<span class="hl-console-h1">')` instead of `function_name('<span class="hl-console-h1">')`.
|
|
best-practices/literal-named-argument:
src/Highlight/Injections/H1Injection.php#L23
Literal argument `'%s%s%s'` 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: '%s%s%s')` instead of `function_name('%s%s%s')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/ChapterView.php#L122
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/Documentation/ChapterView.php#L122
Literal argument `'/^\d+-/'` 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: '/^\d+-/')` instead of `function_name('/^\d+-/')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/ChapterView.php#L122
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/Documentation/ChapterView.php#L40
Literal argument `'/<h3.*>.*<a.*href="(?<h3uri>.*?)".*?<\/span>(?<h3title>.*)<\/a><\/h3>/'` 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: '/<h3.*>.*<a.*href="(?<h3uri>.*?)".*?<\/span>(?<h3title>.*)<\/a><\/h3>/')` instead of `function_name('/<h3.*>.*<a.*href="(?<h3uri>.*?)".*?<\/span>(?<h3title>.*)<\/a><\/h3>/')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/ChapterView.php#L39
Literal argument `'/<h2.*>.*<a.*href="(?<uri>.*?)".*?<\/span>(?<title>.*)<\/a><\/h2>/'` 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: '/<h2.*>.*<a.*href="(?<uri>.*?)".*?<\/span>(?<title>.*)<\/a><\/h2>/')` instead of `function_name('/<h2.*>.*<a.*href="(?<uri>.*?)".*?<\/span>(?<title>.*)<\/a><\/h2>/')`.
|
|
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.
|