You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using the latest version of BLT with Drupal >10.1 I get the following deprecation notice when visiting install.php:
The \Drupal\Component\Assertion\Handle is deprecated in Drupal 10.1.0 and will be removed from Drupal 11.0.0. Instead, replace the calls to \Drupal\Component\Assertion\Handle::register() method with assert_options(ASSERT_EXCEPTION, TRUE).
This seems to break the install process as well, once the batch UI shows up - I think the notice maybe causes the AJAX call to fail?
Describe the solution you'd like
I'd like to see the default assertion handling in settings/default.local.settings.php changed from:
Handle::register();
to
assert_options(ASSERT_EXCEPTION, TRUE);
and the associated use statement removed from the top of the file.
Describe alternatives you've considered
I can manually edit the generated file every time I create a new D10 project.
github-actionsbot
changed the title
Update assertion handling to remove use of deprecated class
BLT-5231: Update assertion handling to remove use of deprecated class
Jan 11, 2024
Is your feature request related to a problem? Please describe.
When using the latest version of BLT with Drupal >10.1 I get the following deprecation notice when visiting
install.php
:The \Drupal\Component\Assertion\Handle is deprecated in Drupal 10.1.0 and will be removed from Drupal 11.0.0. Instead, replace the calls to \Drupal\Component\Assertion\Handle::register() method with assert_options(ASSERT_EXCEPTION, TRUE).
This seems to break the install process as well, once the batch UI shows up - I think the notice maybe causes the AJAX call to fail?
Describe the solution you'd like
I'd like to see the default assertion handling in
settings/default.local.settings.php
changed from:Handle::register();
to
assert_options(ASSERT_EXCEPTION, TRUE);
and the associated
use
statement removed from the top of the file.Describe alternatives you've considered
I can manually edit the generated file every time I create a new D10 project.
Additional context
See here for the Drupal change request - https://www.drupal.org/node/3105918
The text was updated successfully, but these errors were encountered: