Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
TestSiteInstallCommand does not yet provide the property but it's not tested with deprecation messages so we never got to see that warning.
Proposed resolution
Default to stark. I think my patch might be too simple though as it won't trigger the install profile logic anymore.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#18 | 3110874-18.patch | 4.91 KB | andypost |
#18 | interdiff.txt | 3.76 KB | andypost |
#2 | default-theme-3110874-2.patch | 1.82 KB | Berdir |
Comments
Comment #2
BerdirComment #5
andypostComment #6
BerdirMost fails are in simpletest.module, so we could possibly wait on those being removed assuming that will happen?
Comment #7
andypost3 are core tests, remains are simpletest
Comment #9
andypostCan't get how to fix 2 remaining but there 2 more down
Comment #11
longwaveReroll following the removal of Simpletest.
Comment #13
alexpottSo I'm not sure this is the correct change.
I think we should remove the calls to
in \Drupal\TestSite\Commands\TestSiteInstallCommand::installDrupal() - they look meaningless as this is not a test and you don't inherit from it.
To maintain BC we should install classy and set it as the default theme in
\Drupal\TestSite\Commands\TestSiteInstallCommand::installDrupal()
and then we should file an issue to discuss the default theme in tests (like Nightwatch) that use this command.Comment #14
alexpottPostponing this on #3115903: Remove test cruft from TestSiteInstallCommand which addresses #13
Comment #15
lauriii#3115903: Remove test cruft from TestSiteInstallCommand has been committed.
Comment #16
longwaveReroll following #3115903: Remove test cruft from TestSiteInstallCommand, removing the change to TestSiteInstallCommand.
Comment #18
andypostFix the test (
LegacyStyleSheetsRemoveTest
) and I think we could use@inheritdoc
because variable defined in parent classNew exception also documented
Comment #19
longwaveThanks @andypost, changes look good to me and I agree we can use inheritdoc.
Comment #20
andypostI wonder if we should use InvalidArgumentException or DomainException https://www.php.net/manual/en/class.domainexception.php
Comment #22
alexpott@andypost I just pushed and x-posted with you. Feel free to open a follow-up. I don;t think this matters because you're not going to be catching this exception in calling code and doing something else - you going to be fixing your test and moving on.
Committed 305c401 and pushed to 9.0.x. Thanks!
Comment #23
andypostNP, thank you! That's surely runtime exception so no reason to followup