fix: address caster return type typo #100
Merged
Annotations
10 warnings and 7 notices
|
src/Web/Homepage/HomeController.php#L32
Literal argument `'/view'` 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: '/view')` instead of `function_name('/view')`.
|
|
src/Web/Homepage/HomeController.php#L29
Literal argument `'./home.view.php'` 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: './home.view.php')` instead of `function_name('./home.view.php')`.
|
|
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')`.
|
|
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('/')`.
|
|
src/Web/Analytics/PackageDownloadsPerHour/PackageDownloadsPerHourProjector.php#L37
Literal argument `0` 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: 0)` instead of `function_name(0)`.
|
|
src/Web/Analytics/PackageDownloadsPerHour/PackageDownloadsPerHourProjector.php#L37
Literal argument `0` 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: 0)` instead of `function_name(0)`.
|
|
src/Web/Analytics/PackageDownloadsPerHour/PackageDownloadsPerHourProjector.php#L37
Literal argument `'H'` 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: 'H')` instead of `function_name('H')`.
|
|
src/Web/Analytics/PackageDownloadsPerHour/PackageDownloadsPerHourProjector.php#L35
Literal argument `0` 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: 0)` instead of `function_name(0)`.
|
|
src/Web/Analytics/VisitsPerDay/AlterVisitsPerDayTable.php#L16
Literal argument `'date'` 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: 'date')` instead of `function_name('date')`.
|
|
src/Markdown/InlineCodeBlockRenderer.php#L25
Literal argument `'/^\{(?<match>[\w]+)}(?<code>.*)/'` 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: '/^\{(?<match>[\w]+)}(?<code>.*)/')` instead of `function_name('/^\{(?<match>[\w]+)}(?<code>.*)/')`.
|
|
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}`.
|
|
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}`.
|
The logs for this run have expired and are no longer available.
Loading