Expose Composer JSON & Lock file contents #124
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
- Make the `composer.json` and `composer.lock` file paths accessible from the configuration - Make the decoded contents of those two files accessible from the configuration - One file does not require the other - Neither of those files are mandatory but when they are found, they must be valid - Refactored the `ComposerConfiguration` to leverage the new API - The autoloader can now be dumped when adding non-binary files to Box provided the `composer.json` file is given
This was referenced Apr 20, 2018
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.
composer.jsonandcomposer.lockfile paths accessible from the configurationComposerConfigurationto leverage the new APIcomposer.jsonfile is givencomposer.jsonandcomposer.lockfiles to the added files whenever possible