- Issue created by @alison
- 🇺🇸United States alison
If there's maintainer support for moving this module into
mercury_editor/modules, I can submit a MR! - Merge request !53move mercury_editor_setup_test module to "regular" sub-modules directory → (Open) created by alison
- Status changed to Closed: works as designed
10 months ago 10:44pm 19 June 2024 - 🇺🇸United States justin2pin
Hi @alison - to enable test modules, add (or uncomment) this line in your local settings file (i.e. settings.local.php):
$settings['extension_discovery_scan_tests'] = TRUE;Let me know if you still run into issues!
- 🇺🇸United States alison
Oh! Even though it says "test" in the name, it had not occurred to me that this module was meant for testing the module, like for automated tests / debugging -- I thought the intent of this module was more like a demo/example module. I suppose then it would be called Mercury Editor Setup Demo or Mercury Editor Setup Example...
Obviously I'm biased because I didn't know about using test modules like this (to try the module with a demo/starter-setup, not just for automated testing), but, if y'all are going to use this module in how-to presentations, I recommend including an explanation of how to enable the module, or point to documentation about how to enable test modules -- again, I'm biased, but I don't think it's common knowledge among site builders who aren't also contributed module developers.
That said, I get it now, thank you!