Allow packs configuration to be set in one place and defer to packs.yml #48
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
alexevanczuk
commented
Dec 29, 2022
|
|
||
| Packs.all.each do |pack| | ||
| next if pack.relative_path.glob('*.gemspec').any? |
There was a problem hiding this comment.
We don't want to load factories for packs that are gems.
Later, we could consider a first-class API for packs, so this line could be:
next if pack.gem?
alexevanczuk
changed the title
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.
This PR bumps
packs, which allows:Stimpackto configurepacksdirectlypacks.ymlto take precedence forpacksconfiguration if the user is using it, makingstimpack's configuration ofpacksa no-op.