Allow YML configuration to take precedence#7
Merged
alexevanczuk merged 7 commits intoDec 29, 2022
Conversation
alexevanczuk
deleted the
ae-allow-yml-configuration-to-take-precedence
branch
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 idea here is that ideally, users should only use
packs.ymlto configurepacks.In order to not break
stimpackAPI, I wantstimpackto still configurePacksdirectly unlesspacks.ymlexists, in which case we defer to the configuration inpacks.yml.This is intended to be temporary until we migrate Stimpack API to require configuring
packs.yml, at which point we can remove the direct configuration ofpacksand associated code.