2.x update stan #586
ci.yml
on: pull_request
cs-stan
/
Coding Standard & Static Analysis
27s
Matrix: testsuite
Annotations
10 errors and 15 warnings
RiskyTruthyFalsyComparison:
src/AuthenticationService.php#L421
src/AuthenticationService.php:421:14: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
RiskyTruthyFalsyComparison:
src/AuthenticationService.php#L421
src/AuthenticationService.php:421:41: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
PossiblyNullArgument:
src/AuthenticationService.php#L492
src/AuthenticationService.php:492:36: PossiblyNullArgument: Argument 1 of get_class cannot be null, possibly null value provided (see https://psalm.dev/078)
|
RiskyTruthyFalsyComparison:
src/Authenticator/CookieAuthenticator.php#L110
src/Authenticator/CookieAuthenticator.php:110:13: RiskyTruthyFalsyComparison: Operand of type ArrayAccess|array<array-key, mixed>|null contains type array<array-key, mixed>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
RiskyTruthyFalsyComparison:
src/Authenticator/EnvironmentAuthenticator.php#L140
src/Authenticator/EnvironmentAuthenticator.php:140:13: RiskyTruthyFalsyComparison: Operand of type array<array-key, mixed>|null contains type array<array-key, mixed>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
RiskyTruthyFalsyComparison:
src/Authenticator/EnvironmentAuthenticator.php#L150
src/Authenticator/EnvironmentAuthenticator.php:150:13: RiskyTruthyFalsyComparison: Operand of type ArrayAccess|array<array-key, mixed>|null contains type array<array-key, mixed>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
RiskyTruthyFalsyComparison:
src/Authenticator/FormAuthenticator.php#L133
src/Authenticator/FormAuthenticator.php:133:13: RiskyTruthyFalsyComparison: Operand of type ArrayAccess|array<array-key, mixed>|null contains type array<array-key, mixed>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
RiskyTruthyFalsyComparison:
src/Authenticator/HttpDigestAuthenticator.php#L100
src/Authenticator/HttpDigestAuthenticator.php:100:13: RiskyTruthyFalsyComparison: Operand of type ArrayAccess|array<array-key, mixed>|null contains type array<array-key, mixed>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
RiskyTruthyFalsyComparison:
src/Authenticator/HttpDigestAuthenticator.php#L140
src/Authenticator/HttpDigestAuthenticator.php:140:13: RiskyTruthyFalsyComparison: Operand of type non-empty-mixed|null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
RiskyTruthyFalsyComparison:
src/Authenticator/JwtAuthenticator.php#L111
src/Authenticator/JwtAuthenticator.php:111:13: RiskyTruthyFalsyComparison: Operand of type ArrayAccess|array<array-key, mixed>|null contains type array<array-key, mixed>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
|
testsuite (8.1, sqlite)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
testsuite (8.1, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (8.1, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (8.2, sqlite)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
testsuite (8.2, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (8.2, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (7.4, sqlite)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
testsuite (7.4, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (7.4, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (8.0, sqlite)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
testsuite (8.0, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (8.0, sqlite)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (7.4, sqlite, prefer-lowest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
testsuite (7.4, sqlite, prefer-lowest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
testsuite (7.4, sqlite, prefer-lowest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|