- Issue created by @maskedjellybean
I don't know if this is worth fixing, but I wanted to highlight it in case someone else using D10 is confused.
When using Drupal core >=10.3.x but less than 11.x you must use version 3.2.1 of date_recur_modular.
In date_recur_modular composer.json, date_recur is required:
"drupal/date_recur": "^3.8"
This allows requiring date_recur version 3.8.x or 3.9.x.
3.8.x is compatible with D10, 3.9.x is not.
In 3.9.x, the file DrEntityTest.php has been renamed DrEntityTestBasic.php.
Tests provided by date_recur_modular leverage this class for testing.
When a MR is opened for date_recur_modular against the 3.2.x-dev branch, tests are run. However, tests are run using D11 because version 3.2.1 is not constrained to D10 in composer.json:
"drupal/core": ">=10.3",
This means that date_recur 3.9.x is used, which means DrEntityTest.php has been renamed DrEntityTestBasic.php.
In other words, when writing tests locally with D10, DrEntityTest.php will exist and DrEntityTestBasic.php will not. When running tests on an open MR against 3.2.x-dev, DrEntityTest.php will not exist but DrEntityTestBasic.php will. So in order to run tests locally you must temporarily account for this by renaming the file manually or changing the use statements in date_recur_modular.
Active
3.2
Code