chore: redirect /main prefix #99
Merged
Annotations
10 warnings and 7 notices
|
src/Web/Documentation/RedirectMiddleware.php#L44
Literal argument `'version'` 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: 'version')` instead of `function_name('version')`.
|
|
src/Web/Documentation/RedirectMiddleware.php#L40
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('/')`.
|
|
src/Web/Documentation/RedirectMiddleware.php#L40
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+-/')`.
|
|
src/Web/Documentation/RedirectMiddleware.php#L39
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+-/')`.
|
|
src/Web/Documentation/RedirectMiddleware.php#L39
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+-/')`.
|
|
src/Web/Blog/rss.view.php#L26
Literal argument `'c'` 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: 'c')` instead of `function_name('c')`.
|
|
src/Web/Blog/rss.view.php#L10
Literal argument `'c'` 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: 'c')` instead of `function_name('c')`.
|
|
src/Highlight/Injections/ErrorInjection.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>')`.
|
|
src/Highlight/Injections/ErrorInjection.php#L24
Literal argument `'<span class="hl-console-error">'` 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-error">')` instead of `function_name('<span class="hl-console-error">')`.
|
|
src/Highlight/Injections/ErrorInjection.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')`.
|
|
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.
|
|
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.
|
|
src/Markdown/HandleParser.php#L38
Unbraced variable in string interpolation
Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues.
Help: Wrap the variable in curly braces, e.g., `{$variable}`.
|
|
src/Markdown/HandleParser.php#L37
Unbraced variable in string interpolation
Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues.
Help: Wrap the variable in curly braces, e.g., `{$variable}`.
|
|
src/Markdown/HandleParser.php#L36
Unbraced variable in string interpolation
Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues.
Help: Wrap the variable in curly braces, e.g., `{$variable}`.
|
|
src/Markdown/HandleParser.php#L35
Unbraced variable in string interpolation
Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues.
Help: Wrap the variable in curly braces, e.g., `{$variable}`.
|
|
src/Markdown/TempestPackageParser.php#L44
Unbraced variable in string interpolation
Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues.
Help: Wrap the variable in curly braces, e.g., `{$variable}`.
|
The logs for this run have expired and are no longer available.
Loading