Merged
Conversation
…drex/harp into release-v0.17.0
|
In regards to adding more defaults I think With that said I strongly think Harp needs to be able to specify for some files to be Since you already have a config file for Harp I see no reason why you should not just add more properties in that file which define which files these conditions should apply to. |
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
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.
Merge release-v0.16.0 first.
.gitandwww/, thanks @edrexI tried to get #312 in but I think we might want to approach it more like npm: a
.harpignorefile works, config in theharp.jsonworks, or just do nothing and we’ll give you reasonable defaults (namely, no compilingnode_modulesorbower_components). Shelved that for now though.Here’s the draft blog post for the updates, if someone wants to jump in and help me finish it. ;)