feat(docs): fetch docs from monorepository branches #69
coding-conventions.yml
on: pull_request
Run style check
25s
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/Markdown/Symbols/AttributeParser.php#L37
Literal argument `'packages/%s/src'` 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: 'packages/%s/src')` instead of `function_name('packages/%s/src')`.
|
|
best-practices/literal-named-argument:
src/Markdown/Symbols/AttributeParser.php#L37
Literal argument `"/^(\w+)/"` 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: "/^(\w+)/")` instead of `function_name("/^(\w+)/")`.
|
|
best-practices/literal-named-argument:
src/Markdown/Symbols/AttributeParser.php#L19
Literal argument `"{(b)?`#\[((?:\\\{1,2}\w+|\w+\\\{1,2})(?:\w+\\\{0,2})+)\]`}"` 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: "{(b)?`#\[((?:\\\{1,2}\w+|\w+\\\{1,2})(?:\w+\\\{0,2})+)\]`}")` instead of `function_name("{(b)?`#\[((?:\\\{1,2}\w+|\w+\\\{1,2})(?:\w+\\\{0,2})+)\]`}")`.
|
|
best-practices/literal-named-argument:
src/Highlight/Injections/QuestionInjection.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/QuestionInjection.php#L24
Literal argument `'<span class="hl-console-question">'` 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-question">')` instead of `function_name('<span class="hl-console-question">')`.
|
|
best-practices/literal-named-argument:
src/Highlight/Injections/QuestionInjection.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/Markdown/Alerts/AlertBlockRenderer.php#L61
Literal argument `'div'` 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: 'div')` instead of `function_name('div')`.
|
|
best-practices/literal-named-argument:
src/Markdown/Alerts/AlertBlockRenderer.php#L53
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/Markdown/Alerts/AlertBlockRenderer.php#L48
Literal argument `'div'` 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: 'div')` instead of `function_name('div')`.
|
|
best-practices/literal-named-argument:
src/Markdown/Alerts/AlertBlockRenderer.php#L41
Literal argument `'<x-icon :name="$name" class="alert-icon" />'` 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: '<x-icon :name="$name" class="alert-icon" />')` instead of `function_name('<x-icon :name="$name" class="alert-icon" />')`.
|
|
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.
|