Update 02-views.md #51
coding-conventions.yml
on: pull_request
Run style check
32s
Annotations
10 warnings and 5 notices
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L48
Literal argument `'keywords'` 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: 'keywords')` instead of `function_name('keywords')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L47
Literal argument `'title'` 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: 'title')` instead of `function_name('title')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L46
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('')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L46
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+-/')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L46
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')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L45
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('')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L45
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+-/')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L45
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('/')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L45
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('/')`.
|
|
best-practices/literal-named-argument:
src/Web/Documentation/DocumentationIndexer.php#L41
Literal argument `'Documentation entry [%s] is missing a frontmatter.'` 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: 'Documentation entry [%s] is missing a frontmatter.')` instead of `function_name('Documentation entry [%s] is missing a frontmatter.')`.
|
|
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}`.
|