Fix parsing of backtick-enclosed table options #1030
Annotations
20 errors and 1 warning
|
Analyse files with Psalm:
src/Utils/Query.php#L464
src/Utils/Query.php:464:30: PossiblyNullArrayOffset: Cannot access value on variable $clauses using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Utils/Query.php#L418
src/Utils/Query.php:418:22: PossiblyNullArrayOffset: Cannot access value on variable $clauses using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Utils/Formatter.php#L757
src/Utils/Formatter.php:757:72: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Parser::KEYWORD_PARSERS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Utils/Formatter.php#L749
src/Utils/Formatter.php:749:59: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Parser::STATEMENT_PARSERS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Statements/SelectStatement.php#L470
src/Statements/SelectStatement.php:470:23: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Parser::STATEMENT_PARSERS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Statement.php#L279
src/Statement.php:279:23: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Parser::STATEMENT_PARSERS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Parsers/JoinKeywords.php#L101
src/Parsers/JoinKeywords.php:101:39: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Components\JoinKeyword::JOINS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Parsers/JoinKeywords.php#L76
src/Parsers/JoinKeywords.php:76:68: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Components\JoinKeyword::JOINS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Parsers/Expressions.php#L144
src/Parsers/Expressions.php:144:73: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Parser::STATEMENT_PARSERS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with Psalm:
src/Parser.php#L510
src/Parser.php:510:22: PossiblyNullArrayOffset: Cannot access value on variable PhpMyAdmin\SqlParser\Parser::STATEMENT_PARSERS using possibly null offset null|string (see https://psalm.dev/125)
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Parameter \#1 \$string of static method PhpMyAdmin\\SqlParser\\Context\:\:isComment\(\) expects string, mixed given\.$# (argument.type) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Parameter \#1 \$character of static method PhpMyAdmin\\SqlParser\\Context\:\:isWhitespace\(\) expects string, mixed given\.$# (argument.type) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Parameter \#1 \$character of static method PhpMyAdmin\\SqlParser\\Context\:\:isSymbol\(\) expects string, mixed given\.$# (argument.type) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Parameter \#1 \$character of static method PhpMyAdmin\\SqlParser\\Context\:\:isString\(\) expects string, mixed given\.$# (argument.type) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Binary operation "\.\=" between string and mixed results in an error\.$# (assignOp.invalid) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Binary operation "\.\=" between mixed and string results in an error\.$# (assignOp.invalid) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Binary operation "\.\=" between mixed and mixed results in an error\.$# (assignOp.invalid) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Binary operation "\." between string and mixed results in an error\.$# (binaryOp.invalid) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Lexer.php#L0
Ignored error pattern #^Binary operation "\." between mixed and mixed results in an error\.$# (binaryOp.invalid) in path /home/runner/work/sql-parser/sql-parser/src/Lexer.php was not matched in reported errors.
|
|
Analyse files with PHPStan:
src/Components/AlterOperation.php#L62
Ignored error pattern #^Cannot call method remove\(\) on PhpMyAdmin\\SqlParser\\Components\\OptionsArray\|null\.$# (method.nonObject) in path /home/runner/work/sql-parser/sql-parser/src/Components/AlterOperation.php is expected to occur 3 times, but occurred only 1 time.
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Loading