- Issue created by @wim leers
- šØš¦Canada jibran Toronto, Canada
Wim Leers ā credited jibran ā .
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
I marked this because I first thought this should be committed after š Configuration schema & required values: add test coverage for `nullable: true` validation support Fixed . But I just realized that is not necessary, the two can land in whichever order. š
Also crediting @jibran explicitly for surfacing this so incredibly early over at #3361534-90: KernelTestBase::$strictConfigSchema = TRUE and BrowserTestBase::$strictConfigSchema = TRUE do not actually strictly validate ā ! š¤Æ
- Open on Drupal.org āEnvironment: PHP 8.2 & MySQL 8last update
over 1 year ago Not currently mergeable. - @wim-leers opened merge request.
- last update
over 1 year ago 29,953 pass - Issue was unassigned.
- Status changed to Needs review
over 1 year ago 8:45am 8 August 2023 - š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
This cannot be tested automatically, only manually. Otherwise, we'd need a custom mechanism to detect contrib vs core extensions.
The steps to reproduce in the issue summary are how this can be manually tested.
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
This is now a blocker for #3341682 per @catch at #3341682-56: [PP-1] New config schema data type: `required_label` ā .
- šŗšøUnited States phenaproxima Massachusetts
I followed the steps to test this, and confirmed that before this patch, the Dynamic Entity Reference test fails, and passes (with deprecations) after. So, works exactly as advertised!
- Status changed to Needs work
over 1 year ago 12:43pm 11 August 2023 - šŗšøUnited States phenaproxima Massachusetts
Patch looks great, just a couple of questions.
- last update
over 1 year ago 29,958 pass - Status changed to Needs review
over 1 year ago 7:40am 14 August 2023 - š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
- implemented @phenaproxima's excellent suggestions
- went ahead and already updated the CR ā : https://www.drupal.org/node/3362879#contrib ā , but holding off for core committer approval to also tweak the release notes snippet and move the release highlights tag
- Status changed to RTBC
over 1 year ago 12:08pm 14 August 2023 - Status changed to Fixed
over 1 year ago 12:52pm 14 August 2023 - š«š®Finland lauriii Finland
Makes sense to convert these to deprecation failures to reduce the disruption. I guess this sets a pattern that from 11.x onwards, if we introduce additional validation constraints, we'd have to introduce them as deprecations first. If that's the case, we'll need to figure out how to do that but we don't have to cross that bridge yet.
Committed 4c8821b and pushed to 11.x. Thanks!
-
lauriii ā
committed 4c8821bc on 11.x
Issue #3379899 by Wim Leers, phenaproxima, jibran, borisson_: Follow-up...
-
lauriii ā
committed 4c8821bc on 11.x
- š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
YAY!
Updated the release notes at š KernelTestBase::$strictConfigSchema = TRUE and BrowserTestBase::$strictConfigSchema = TRUE do not actually strictly validate Fixed and moved the tag there.
This unblocked š New config schema data type: `required_label` Fixed š
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
about 1 year ago 7:58am 19 October 2023 - š§šŖBelgium wim leers Ghent š§šŖšŖšŗ
Refining this further: š Follow-up for #3361534: config validation errors in contrib modules should not cause deprecation notices, unless they opt in Active .