Setting deploy mode to production with --skip-compilation flag should not clear generated code #16211
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changing the deploy mode to production using the
--skip-compilation
flag will remove the generated code ingenerated/code/
andgenerated/metadata/
.The expected result is that
generated/code/
andgenerated/metadata/
should not be cleared.This was introduced in ea57b46#diff-de930b059902896ae8ce118b11024cbaR108. It is safe to remove as the
deploy:mode:set
command will clear the folder when the--skip-compilation
flag is not used.Manual testing scenarios
php bin/magento deploy:mode:set developer
php bin/magento setup:di:compile
php bin/magento deploy:mode:set production --skip-compilation
ls -la generated/metadata/
should contain files