Generate gem specific sources in lockfile #1402
Merged
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.
The gem specific sources are ignored when:
gems
section prior to the gemFor example:
X
is added to the lockfile beforeY
source
definition ofY
is ignored because it's traversed as a dependency ofX
Y
is skipped from thegems
section, because it's already added to the lockfile (without customsource
section)This PR fixes the problem by introducing
gem_entries
hash and referees theignore
andsource
attribute through it instead of passing it as method arguments.