[Config] Multiple presets in config #140
Open
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
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.
What:
Description:
After creating 2 more stubs containing currency codes and country codes, the default peck preset started to have a lot of stuff that may be unnecessary for a project
This PR aims to change the configuration so that it is possible to use more than 1 preset at the same time, so the dev can choose which presets to use to ignore words by default
With this change, the base preset will always be used, and the user will be able to use extra presets if desired.
This PR contains a breaking change in the
peck.jsonfile, where thepresetproperty was renamed topresetsto make more sense with what this property receives in this new version.Related:
#138