docs: fix typo in views #90
Merged
Annotations
10 warnings and 5 notices
|
src/Web/Analytics/PackageDownloadsPerDay/CreatePackageDownloadsPerDayTable.php#L20
Literal argument `'package'` 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: 'package')` instead of `function_name('package')`.
|
|
src/Web/Analytics/PackageDownloadsPerDay/CreatePackageDownloadsPerDayTable.php#L19
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/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')`.
|
|
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')`.
|
|
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')`.
|
|
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')`.
|
|
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')`.
|
|
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')`.
|
|
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')`.
|
|
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')`.
|
|
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