Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
39 commits
Select commit Hold shift + click to select a range
f17cf7f
Build/Test Tools: Include the PHPStan baselines through a PHP loader.
westonruter Nov 17, 2026
188cf53
Build/Test Tools: Suppress the PHPStan baselines through the loader.
westonruter Nov 17, 2026
5dcf22c
Build/Test Tools: Normalize the output directory once when stripping …
westonruter Nov 17, 2026
b2e1a4e
Build/Test Tools: Give a PHPStan baselines directory its own loader.
westonruter Nov 17, 2026
77856d1
Build/Test Tools: Only load PHPStan baselines named for an identifier.
westonruter Nov 17, 2026
4d365ca
Build/Test Tools: Stop stripping baseline includes from the PHPStan c…
westonruter Nov 17, 2026
6d34b30
Build/Test Tools: Update docs for the PHPStan baselines loader.
westonruter Nov 17, 2026
e46fbbb
Build/Test Tools: Only suppress PHPStan baselines when generating them.
westonruter Nov 17, 2026
8e5f885
Build/Test Tools: Keep the PHPStan baselines loader docblock true whe…
westonruter Nov 17, 2026
b5c79e2
Merge branch 'trunk' into phpstan-baseline-loader
westonruter Nov 17, 2026
9e9c3ef
Build/Test Tools: Only suppress the PHPStan baselines being regenerated.
westonruter Nov 17, 2026
61ccde1
Build/Test Tools: Accept an empty PHPStan baseline when regenerating.
westonruter Nov 17, 2026
c8c39a4
Build/Test Tools: Restore the alignment of an assignment in the basel…
westonruter Nov 17, 2026
04c4cc0
Build/Test Tools: Include the PHPStan baselines by bare file name.
westonruter Nov 17, 2026
2ce88ce
Build/Test Tools: Share the PHPStan baselines loader logic in one place.
westonruter Nov 17, 2026
2816573
Build/Test Tools: Say when other PHPStan baselines stay in force whil…
westonruter Nov 17, 2026
280eb7d
Build/Test Tools: Resolve both ends of a PHPStan baselines loader's r…
westonruter Nov 17, 2026
430638b
Build/Test Tools: Say other PHPStan baselines stay in force for any n…
westonruter Nov 17, 2026
c972e54
Build/Test Tools: Rewrite the PHPStan baselines loader on every regen…
westonruter Nov 17, 2026
11dd05a
Build/Test Tools: List the PHPStan baselines directory rather than gl…
westonruter Nov 17, 2026
953f66c
Build/Test Tools: Reject a PHPStan baselines `--identifier` that is n…
westonruter Nov 17, 2026
3563d3b
Build/Test Tools: Rewrap the `--output-dir` help of the PHPStan basel…
westonruter Nov 17, 2026
25ab64b
Build/Test Tools: Only name an existing output directory to the PHPSt…
westonruter Nov 17, 2026
30d2ef7
Build/Test Tools: Compare PHPStan baselines directories by identity, …
westonruter Nov 17, 2026
5505675
Build/Test Tools: Clear an inherited WP_PHPSTAN_GENERATING_BASELINES …
westonruter Nov 17, 2026
0d03b73
Build/Test Tools: Report an unlistable PHPStan baselines directory wi…
westonruter Nov 17, 2026
54af27b
Build/Test Tools: Only delete PHPStan baselines the generator wrote.
westonruter Nov 17, 2026
354a2e7
Build/Test Tools: Stop when a PHPStan baseline cannot be written.
westonruter Nov 17, 2026
9c03be1
Build/Test Tools: Correct what the PHPStan baseline header says regen…
westonruter Nov 17, 2026
5a5af73
Build/Test Tools: Refuse a PHPStan baselines output directory holding…
westonruter Nov 17, 2026
e266df1
Build/Test Tools: Cast substr() when building a PHPStan baselines loa…
westonruter Nov 17, 2026
d11b05d
Build/Test Tools: Recognize a PHPStan baseline's header with CRLF lin…
westonruter Nov 17, 2026
a91ec5e
Build/Test Tools: Refuse to replace a `loader.php` the PHPStan baseli…
westonruter Nov 17, 2026
3bd04cd
Build/Test Tools: Name the configuration and directory in a PHPStan b…
westonruter Nov 17, 2026
3e993b0
Build/Test Tools: Anchor the PHPStan baseline file name pattern at th…
westonruter Nov 17, 2026
5e5fafa
Build/Test Tools: Drop the PHPStan baselines retire loop's own header…
westonruter Nov 17, 2026
76d02fa
Build/Test Tools: Drop the PHPStan baselines hardening against misuse.
westonruter Nov 17, 2026
f2f7f16
Build/Test Tools: Say which PHPStan baselines the generator suppresses.
westonruter Nov 17, 2026
aaa1cd1
Use import RuntimeException
westonruter Nov 17, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/reusable-phpstan-static-analysis-v1.yml
Original file line number Diff line number Diff line change
Expand Up @@ -283,9 +283,9 @@ jobs:
composer phpstan:fix
```

That runs PHPStan with `--fix`, which lowers the counts in the files under [`tests/phpstan/baselines`][baselines], removes the entries that no longer match, and removes any `@phpstan-ignore` annotation in the code that no longer ignores anything. It then deletes any baseline left with no entries, and updates the list of them in `phpstan.neon.dist`.
That runs PHPStan with `--fix`, which lowers the counts in the files under [`tests/phpstan/baselines`][baselines], removes the entries that no longer match, and removes any `@phpstan-ignore` annotation in the code that no longer ignores anything. It then deletes any baseline left with no entries.

Alternatively, regenerate the baselines with `npm run typecheck:php:baselines` or `composer phpstan:baselines`. That also deletes any baseline whose errors are now all fixed, and updates the list of them in `phpstan.neon.dist`, but it does not clear an `@phpstan-ignore` annotation.
Alternatively, regenerate the baselines with `npm run typecheck:php:baselines` or `composer phpstan:baselines`. That also deletes any baseline whose errors are now all fixed, but it does not clear an `@phpstan-ignore` annotation.

See [`tests/phpstan/README.md`][readme] for details.

Expand Down
40 changes: 4 additions & 36 deletions phpstan.neon.dist
Original file line number Diff line number Diff line change
Expand Up @@ -18,44 +18,12 @@ includes:

# Preexisting errors that should be ignored, one baseline per error identifier
# so that the remaining work on each is visible as a single shrinking file.
# Each is meant to reach zero and be deleted, taking its line below with it.
# Each is meant to reach zero and be deleted.
# https://phpstan.org/user-guide/baseline
#
# Regenerate with `composer phpstan:baselines`, which rewrites both the files
# and the list between the markers. Do not edit that list by hand.
# phpstan:baselines start
- tests/phpstan/baselines/argument.type.neon
- tests/phpstan/baselines/argument.unresolvableType.neon
- tests/phpstan/baselines/assign.propertyType.neon
- tests/phpstan/baselines/binaryOp.invalid.neon
- tests/phpstan/baselines/booleanAnd.leftAlwaysTrue.neon
- tests/phpstan/baselines/booleanNot.alwaysTrue.neon
- tests/phpstan/baselines/class.notFound.neon
- tests/phpstan/baselines/deadCode.unreachable.neon
- tests/phpstan/baselines/empty.property.neon
- tests/phpstan/baselines/empty.variable.neon
- tests/phpstan/baselines/function.alreadyNarrowedType.neon
- tests/phpstan/baselines/function.resultUnused.neon
- tests/phpstan/baselines/identical.alwaysFalse.neon
- tests/phpstan/baselines/if.alwaysFalse.neon
- tests/phpstan/baselines/if.alwaysTrue.neon
- tests/phpstan/baselines/isset.property.neon
- tests/phpstan/baselines/method.childParameterType.neon
- tests/phpstan/baselines/method.unused.neon
- tests/phpstan/baselines/notIdentical.alwaysTrue.neon
- tests/phpstan/baselines/offsetAccess.nonOffsetAccessible.neon
- tests/phpstan/baselines/offsetAccess.notFound.neon
- tests/phpstan/baselines/offsetAssign.valueType.neon
- tests/phpstan/baselines/parameterByRef.type.neon
- tests/phpstan/baselines/parameterByRef.unusedType.neon
- tests/phpstan/baselines/property.defaultValue.neon
- tests/phpstan/baselines/property.nonObject.neon
- tests/phpstan/baselines/property.notFound.neon
- tests/phpstan/baselines/property.private.neon
- tests/phpstan/baselines/return.type.neon
- tests/phpstan/baselines/varTag.noVariable.neon
- tests/phpstan/baselines/variable.undefined.neon
# phpstan:baselines end
# The loader includes every baseline in its directory, so adding or deleting one
# needs no edit here. Regenerate them with `composer phpstan:baselines`.
- tests/phpstan/baselines/loader.php

# Rules from phpstan-strict-rules which core already complies with, or which enforce the
# WordPress Coding Standards. The others are not enabled until the code complies with them,
Expand Down
6 changes: 4 additions & 2 deletions tests/phpstan/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -204,6 +204,8 @@ PHPStan errors can be ignored in the following ways:

The baselines live in [`baselines/`](baselines), one file per error identifier, such as `variable.undefined.neon`. Splitting them this way keeps each kind of error visible as a single file that should shrink to nothing and then be deleted, rather than as part of one large file in which every kind is mixed together.

[`phpstan.neon.dist`](../../phpstan.neon.dist) does not list the baselines one by one. It includes [`baselines/loader.php`](baselines/loader.php), which includes every `.neon` file in that directory named for an error identifier, so a baseline takes effect as soon as it is added, and stops as soon as it is deleted, without an edit of the configuration.

Every entry is scoped to the file the error occurs in and carries an exact occurrence count:

```neon
Expand Down Expand Up @@ -235,7 +237,7 @@ composer phpstan:fix
This runs three steps, each only when the one before it succeeds:

1. PHPStan with its `--fix` option, which lowers the count of the entry, or removes the entry, leaving the rest of the baseline as it was. It is usually much faster than regenerating, since it reuses the result cache of the run that reported the errors. Unlike regenerating, it also removes an `@phpstan-ignore` comment that no longer matches.
2. `composer phpstan:baselines -- --prune`, which deletes any baseline left with no entries, along with its `includes` entry in `phpstan.neon.dist`. Removing the last entry of a baseline leaves the file behind, as `ignoreErrors: []`. Pruning analyzes nothing, so it can also be run on its own.
2. `composer phpstan:baselines -- --prune`, which deletes any baseline left with no entries. Removing the last entry of a baseline leaves the file behind, as `ignoreErrors: []`. Pruning analyzes nothing, so it can also be run on its own.
3. The analysis once more, which reuses the result cache and so is quick. PHPStan's `--fix` reports only what it fixed, and succeeds even when other errors remain, so this is what shows the errors that are left.

Keep in mind:
Expand Down Expand Up @@ -290,7 +292,7 @@ composer phpstan:baselines -- --help

Note the `--` in each of those. Composer needs it in order to pass the flags on to the script rather than reading them as its own, and without it they are discarded silently, so `composer phpstan:baselines --identifier=variable.undefined` regenerates every baseline rather than that one. The npm script supplies it, which is why only one is needed there.

A run also deletes any baseline whose identifier no longer reports anything, and rewrites the list of them between the `# phpstan:baselines` markers in the `includes` of [`phpstan.neon.dist`](../../phpstan.neon.dist) to match. Adding a newly split out baseline, and retiring one that has reached zero, therefore need no edit of the configuration.
A run also deletes any baseline whose identifier no longer reports anything. Since the baselines are included through [`baselines/loader.php`](baselines/loader.php), adding a newly split out baseline, and retiring one that has reached zero, need no edit of the configuration.

PHPStan's own `--generate-baseline` is deliberately not used directly. It captures every error a run reports, with no way to restrict it to one identifier, so it cannot refresh a single baseline without sweeping every other kind of error into it.

Expand Down
105 changes: 105 additions & 0 deletions tests/phpstan/baseline-includes.php
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
<?php
/**
* Finds the PHPStan baselines in a directory.
*
* Every baselines directory has a `loader.php`, which a configuration includes
* rather than listing the baselines one by one, so that adding a baseline, or
* deleting one that has reached zero, needs no edit of the configuration. A NEON
* configuration can only include files by name, but a PHP one returns the same
* structure and can find them itself. Each loader requires this file and returns
* get_baseline_includes() for its own directory, and `generate-baselines.php`
* requires it too, so the loaders and the generator agree on what a baseline is.
*
* PHPStan keys its cache of the configuration on the files it includes, so a
* baseline added or deleted takes effect on the next run.
*
* @package WordPress
*/

namespace WordPress\PHPStan;

use RuntimeException;

/**
* Environment variable that tells a baselines loader to include nothing.
*
* `composer phpstan:baselines` sets it to the directory it is writing baselines
* to while it analyzes, so that the errors those baselines suppress are reported
* again for it to write back out. It is the directory's real path, which is what
* each loader's __DIR__ is, and each loader compares it with its own, so this
* works however the configuration includes the loader, even through another
* configuration that includes the one that includes it.
*
* The baselines in any other directory stay in force. Those regenerated are then
* only the errors the others leave, so that an error is baselined once: the
* baselines of a stricter configuration that includes `phpstan.neon.dist` hold
* what its baselines do not. Any other value, such as a variable left set by
* mistake, matches no directory.
*/
const GENERATING_BASELINES_ENV = 'WP_PHPSTAN_GENERATING_BASELINES';

/**
* Pattern matching the file name of a baseline.
*
* The name is the error identifier, matched as PHPStan validates identifiers,
* followed by `.neon`, so that a stray file such as a merge tool's
* `argument.type_BACKUP_1234.neon` is neither loaded nor retired. It ends in `\z`
* rather than `$`, which would also match a name ending in a newline.
*/
const BASELINE_FILE_PATTERN = '/^[a-zA-Z0-9](?:[a-zA-Z0-9.]*[a-zA-Z0-9])?\.neon\z/';

/**
* Lists the per-identifier baselines present on disk.
*
* The directory is listed rather than globbed, since glob() would read any of its
* metacharacters in the directory's own path, such as the brackets of a checkout
* in `wp [old]/`, as a pattern, and match nothing.
*
* A directory that cannot be listed is an error rather than one with no
* baselines, since treating it as empty would drop every suppression at once,
* with nothing to say why.
*
* @param non-empty-string $directory Absolute path to the baseline directory.
* @return list<non-empty-string> File names, sorted.
*
* @throws RuntimeException When the directory cannot be listed.
*/
function find_baselines( string $directory ): array {
$entries = is_dir( $directory ) ? scandir( $directory ) : false;

if ( false === $entries ) {
throw new RuntimeException( "Could not list the PHPStan baselines in $directory." );
}

$names = array();
foreach ( $entries as $name ) {
if ( '' !== $name && 1 === preg_match( BASELINE_FILE_PATTERN, $name ) ) {
$names[] = $name;
}
}

return $names;
}

/**
* Returns the configuration a baselines loader hands to PHPStan.
*
* Each baseline is included by its bare file name, which PHPStan resolves against
* the loader's path as the configuration reached it. A loader's __DIR__ is the
* real path, with any symbolic link resolved, so an absolute path built from it
* would place the baselines, and the paths their entries name relative to
* themselves, outside a checkout reached through a link, where they match none
* of the analyzed files.
*
* @param non-empty-string $directory The loader's directory, as its __DIR__.
* @return array{includes: list<non-empty-string>} Configuration.
*
* @throws RuntimeException When the directory cannot be listed.
*/
function get_baseline_includes( string $directory ): array {
if ( getenv( GENERATING_BASELINES_ENV ) === $directory ) {
return array( 'includes' => array() );
}

return array( 'includes' => find_baselines( $directory ) );
}
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/argument.type.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=argument.type
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/argument.unresolvableType.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=argument.unresolvableType
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/assign.propertyType.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=assign.propertyType
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/binaryOp.invalid.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=binaryOp.invalid
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/booleanAnd.leftAlwaysTrue.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=booleanAnd.leftAlwaysTrue
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/booleanNot.alwaysTrue.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=booleanNot.alwaysTrue
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/class.notFound.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=class.notFound
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/deadCode.unreachable.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=deadCode.unreachable
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/empty.property.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=empty.property
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/empty.variable.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=empty.variable
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
6 changes: 3 additions & 3 deletions tests/phpstan/baselines/function.alreadyNarrowedType.neon
Original file line number Diff line number Diff line change
Expand Up @@ -7,14 +7,14 @@
# silently. Fixing an occurrence therefore means decrementing or removing its
# entry here as part of the same change.
#
# The goal is to empty this file and delete it, along with the `includes` entry
# for it in phpstan.neon.dist.
# The goal is to empty this file and delete it.
#
# Generated by `composer phpstan:baselines`. Do not edit by hand; regenerate with
#
# composer phpstan:baselines -- --identifier=function.alreadyNarrowedType
#
# which reruns the analysis with this file suppressed so the errors surface again.
# which reruns the analysis with the baselines in this directory suppressed, so
# that their errors surface again, and rewrites only this file.

parameters:
ignoreErrors:
Expand Down
Loading
Loading