-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good start. I've suggested some clarifications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good, I have a minor suggestion to help the documentation flow well together.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Let's give @ericwb a chance to review before we merge.
We should merge first pull request number 213 before this one. |
There is no need to put "which has to be merged first." in PR message bodies. If there is a dependency, create the dependency using a git rebase. |
"We need documentation for the exclude option and how a user can user globs." - This statement is strange. It sounds as if this is an issue, not a fix. |
docs/configuration.md
Outdated
Precaution uses a variety of tools under the hood without exposing | ||
implementation details and complexity of the underlying tools to the user. | ||
|
||
Concretely, this means that Precaution ignores any tool specific configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why "concretely"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because of this sentence is connected with the statement above.
“Precaution uses a variety of linters under the hood without exposing
implementation details and complexity of the underlying tools to the user and because of that we ignore linter specific configuration files”.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like and because of that better than having a separate statement starting with "concretely".
I think even better would be to expand on the reasoning a bit.
Precaution uses a variety of linters under the hood without exposing implementation details and complexity of the underlying tools to the user. Because of that, and in order to prevent conflict with any configuration files which may exist in the target git repository, Precaution ignores any linter specific configuration files.
I updated my pr with the suggestion from @joshuagl about the Glob syntax in the exclude option. |
I updated my pr with the last suggestions from @joshuagl #222 (comment). |
Codecov Report
@@ Coverage Diff @@
## master #222 +/- ##
======================================
Coverage 98.3% 98.3%
======================================
Files 18 18
Lines 353 353
Branches 38 38
======================================
Hits 347 347
Misses 6 6 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking good, thanks
Related to pull request #213 which has to be merged first. We need documentation for the exclude option and how a user can user globs. Signed-off-by: Martin Vrachev <mvrachev@vmware.com>
Related to pull request #213
which has to be merged first.
We need documentation for the exclude option and how a user can user
globs.
Signed-off-by: Martin Vrachev mvrachev@vmware.com