Fix #52. Scan entire file tree for config by default. #55
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
Also, add jshint.scanProjectOnly extension pref. When set to true would only scan up to the project root.
cfjedimaster
added a commit
that referenced
this pull request
Jun 5, 2014
Fix #52. Scan entire file tree for config by default.
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.
Fix #52. Scan entire file tree for config.
Also, add jshint.scanProjectOnly extension pref. When set to
truewould only scan up to the project root. The default isfalse-- scan the entire tree up to the root.In order to set the pref to limit the scan to project subtree, add the following to your brackets.json or to project's .brackets.json:
cc: @cfjedimaster