Skip to content

docs: fix typo in views #50

docs: fix typo in views

docs: fix typo in views #50

Triggered via pull request June 28, 2025 06:14
Status Success
Total duration 27s
Artifacts

coding-conventions.yml

on: pull_request
Run style check
23s
Run style check
Fit to window
Zoom out
Zoom in

Annotations

10 warnings and 5 notices
best-practices/literal-named-argument: src/Web/Analytics/VisitsPerDay/VisitsPerDayProjector.php#L34
Literal argument `'Y-m-d H:i: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: 'Y-m-d H:i:s')` instead of `function_name('Y-m-d H:i:s')`.
best-practices/literal-named-argument: src/Web/Analytics/VisitsPerDay/VisitsPerDayProjector.php#L34
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')`.
best-practices/literal-named-argument: src/Web/Analytics/VisitsPerDay/VisitsPerDayProjector.php#L31
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)`.
best-practices/literal-named-argument: src/Web/Analytics/VisitsPerDay/VisitsPerDayProjector.php#L31
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)`.
best-practices/literal-named-argument: src/GitHub/GetLatestRelease.php#L28
Literal argument `'https://api.github.com/repos/tempestphp/tempest-framework/releases/latest'` 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: 'https://api.github.com/repos/tempestphp/tempest-framework/releases/latest')` instead of `function_name('https://api.github.com/repos/tempestphp/tempest-framework/releases/latest')`.
best-practices/literal-named-argument: src/GitHub/GetLatestRelease.php#L24
Literal argument `'v%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: 'v%s')` instead of `function_name('v%s')`.
best-practices/literal-named-argument: src/GitHub/GetLatestRelease.php#L19
Literal argument `'TEMPEST_BUILD_LATEST_RELEASE'` 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: 'TEMPEST_BUILD_LATEST_RELEASE')` instead of `function_name('TEMPEST_BUILD_LATEST_RELEASE')`.
best-practices/literal-named-argument: src/Highlight/Injections/EmphasizeInjection.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/EmphasizeInjection.php#L24
Literal argument `'<span class="hl-console-em">'` 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-em">')` instead of `function_name('<span class="hl-console-em">')`.
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')`.
consistency/string-interpolation-braces: 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}`.
consistency/string-interpolation-braces: 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}`.
consistency/string-interpolation-braces: 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}`.
consistency/string-interpolation-braces: 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}`.
consistency/string-interpolation-braces: 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}`.