Problem/Motivation
Follow-up to #3341974: Finalize \Drupal\automatic_updates\Development\Converter script to update core MR
I think for the Core Alpha version of Package Manager it is ok to have package_manager/tests/fixtures/fake_site as it is but for beta we should also have the script to recreate it.
Proposed resolution
the core version of ComposerFixtureCreator will need
- to be moved to core/scripts I guess?
Right now core's composer.json has
"autoload-dev": { "psr-4": { "Drupal\\Composer\\": "composer" } },Not sure if we could just add
"Drupal\\PackageManager\\": "core/modules/package_manager/scripts"Are modules not suppose to have their own development scripts?
I seecore/scripts/js/ckeditor5-check-plugins.jsso this doesn't live in the module. But this is JS script with the composer.json able to setautoload-devit would seem pretty easy for our script to live in our module - Instead of using a script argument to find base of core just use the relative path from where ever the script is moved
Comments
Comment #2
tedbowComment #3
wim leersAre you saying it would be okay to not have the fixture creator in the MR at #3253158: Add Alpha level Experimental Update Manager module? I very much doubt that. That'd mean core requires some contrib script? 😅
IMHO this is something that is in the scope of #3341974: Finalize \Drupal\automatic_updates\Development\Converter script to update core MR to fix?
Comment #4
tedbowok closing this as a duplicate of #3341974: Finalize \Drupal\automatic_updates\Development\Converter script to update core MR