Now that VariationCache is part of Drupal core 10.2 we want people to use the core version instead. However, until all modules using VariationCache can update their minimum requirement to Drupal 10.2 or greater, we need to make sure that they can still use the old namespace (\Drupal\variationcache\foo) without issues.

Therefore, we should move the current classes to an Old folder and point to the core classes if available. If the core classes do not exist, it means we are on a lower Drupal core version and we can make the old namespaced classes point to the Old folder. All of this is done in the .module file by using class_alias, which is an officially supported practice used for experimental modules in core.

See: this part of the experimental documentation

Comments

kristiaanvandeneynde created an issue. See original summary.

kristiaanvandeneynde’s picture

Status: Active » Needs review
StatusFileSize
new26.84 KB

Removes the only test we had because it's now tested in core.

Status: Needs review » Needs work

The last submitted patch, 2: variationcache-3381673-2.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

kristiaanvandeneynde’s picture

Status: Needs work » Fixed

Group tests seem to run fine on my local with D10.1 and D10.2 combined with this version of VariationCache, so releasing the final version.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.