Documentation clarification: COMPOSER_NO_DEV scope #11447
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
COMPOSER_NO_DEV applies to composer require as well.
|
Makes sense thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates documentation of COMPOSER_NO_DEV variable.
Further to: 10995
Currently the --update-no-dev option links to the documentation for COMPOSER_NO_DEV.
The documentation for COMPOSER_NO_DEV only references the --no-dev option for install and update. The option above it (COMPOSER_NO_AUDIT) references require so it makes it seem as though perhaps this doesn't apply to require - although it would be strange if it did not.
Testing suggest that it does in fact work as indicated on the --update-no-dev option.
Before
After
Referenced require first as otherwise it seems less confusing with multiple levels of or.