This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
Support for configuration file #21
Closed
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
Added setting for path to configuration file. If set, it's passed to the linter command.
|
Do you know that I guess this might be useful if you need to use a nonstandard file name for some reason, but I'm curious how necessary it is. |
|
We had a project where it would be nice to hide the file, eg Issue #16 might be related? |
|
Closing this in favour of #24 which was just merged. Thanks anyway! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Added setting for path to configuration file. If set, it's passed to the linter command.
Would you be interested in pulling this in to the main repo? Please let me know if you have any feedback!