Skip to content

Force CreateProjectCommand to use the installed composer.json #11493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 7, 2023
Merged

Force CreateProjectCommand to use the installed composer.json #11493

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6ea7e3f
Force CreateProjectCommand to use the installed composer.json
aschempp Jun 5, 2023
2d79c0d
Check if a new composer.json file exists
aschempp Jun 7, 2023
acaa830
Add comment
Seldaek Jun 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/Composer/Command/CreateProjectCommand.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -469,6 +469,13 @@ protected function installRootPackage(IOInterface $io, Config $config, string $p
$io->writeError('<info>Created project in ' . $directory . '</info>');
chdir($directory);

// ensure that the env var being set does not interfere with create-project
// as it is probably not meant to be used here, so we do not use it if a composer.json can be found
// in the project
if (file_exists($directory.'/composer.json')) {
Platform::putEnv('COMPOSER', $directory.'/composer.json');
}

Platform::putEnv('COMPOSER_ROOT_VERSION', $package->getPrettyVersion());

// once the root project is fully initialized, we do not need to wipe everything on user abort anymore even if it happens during deps install
Expand Down