Discovered in 📌 Configuration schema & required values: add test coverage for `nullable: true` validation support Fixed .
For example:
1) Drupal\Tests\system\Functional\Datetime\DrupalDateTimeTest::testDateTimezone
Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for system.date with the following errors: 0 [timezone.default] This value should not be null.
Run Drupal core's test suite with 📌 Configuration schema & required values: add test coverage for `nullable: true` validation support Fixed applied, and with the lines
'system.date' => [
// @todo Fix config or tweak schema of `type: system.date`.
// @see system.schema.yml
'timezone.default' => [
'This value should not be null.',
],
],
removed from \Drupal\Core\Config\Schema\SchemaCheckTrait::checkConfigSchema().
Solution: fix invalid config schema: it should allow timezone.default to be null: add nullable: true. Why? Because:
\Drupal\Tests\system\Functional\Datetime\DrupalDateTimeTest::testDateTimezone() this seems intentional
timezone.default: 0 in core/modules/system/config/install/system.date.yml, zero and null seem to behave the same
TBD
None.
None.
None.
N/A
Closed: outdated
11.0 🔥
I think this is not an issue anymore and can be closed as outdated. Moving it to NR, so as to get more eyes on it.
We no longer have the array of ignore things in ChemaCheckTrait, as far as I can see, so I think you're right that this can be closed.