Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for analysing more than one input file #1

Closed
ghost opened this issue Feb 25, 2016 · 0 comments
Closed

Add support for analysing more than one input file #1

ghost opened this issue Feb 25, 2016 · 0 comments

Comments

@ghost
Copy link

ghost commented Feb 25, 2016

Aggregate the results in a useful way so the file maps to the results conveniently.

ghost pushed a commit that referenced this issue Feb 25, 2016
… and aggregating the results

also drop the notion of "fatal violation" as far as the end user is concerned.  it does stop processing for that file, but just gets logged as a "failing violation".  Given that multiple files could be processed at the same time, exiting out abruptly because one particular file has a "fatal" violation is no good - thus the stop processing flag in its stead.

update the command line argument to better reflect its a path to the json instead of an actual json string
ghost pushed a commit that referenced this issue Feb 25, 2016
… lint-ing

also make sure paths are String, not File
@ghost ghost closed this as completed Feb 25, 2016
ghost pushed a commit that referenced this issue Feb 25, 2016
jesseadams pushed a commit that referenced this issue Apr 12, 2019
Iterations:

1. 100 max
2. 90 max
3. 80 max (final iteration)
ghost pushed a commit that referenced this issue Apr 13, 2019
* Refactoring for Metrics/LineLength Iteration #1

Iterations:

1. 100 max
2. 90 max
3. 80 max (final iteration)

* #170 i bumped the metric up a bit... we all have wide screens and i like the way some code reads that is a hair long than 100.  also use more natural and consistent select calls for a few of the rules
ghost pushed a commit that referenced this issue Apr 18, 2019
* Refactoring for Metrics/LineLength Iteration #1

Iterations:

1. 100 max
2. 90 max
3. 80 max (final iteration)

* #170 i bumped the metric up a bit... we all have wide screens and i like the way some code reads that is a hair long than 100.  also use more natural and consistent select calls for a few of the rules

* Refactoring for the following lint class cops

* Lint/UnusedMethodArgument
* Lint/RescueException
* Lint/UnusedBlockArgument
* Lint/StringConversionInInterpolation

* Rebasing from master

* #170 use select to clean up auth rule.  Add ScriptError to protect from broken custom rules
ghost pushed a commit that referenced this issue Apr 18, 2019
* Fixing various rubocop violations

Made exceptions for some

* Adding dockerfile for future DockerHub publishing (#168)

* Refactoring for the following lint class cops (#173)

* Refactoring for Metrics/LineLength Iteration #1

Iterations:

1. 100 max
2. 90 max
3. 80 max (final iteration)

* #170 i bumped the metric up a bit... we all have wide screens and i like the way some code reads that is a hair long than 100.  also use more natural and consistent select calls for a few of the rules

* Refactoring for the following lint class cops

* Lint/UnusedMethodArgument
* Lint/RescueException
* Lint/UnusedBlockArgument
* Lint/StringConversionInInterpolation

* Rebasing from master

* #170 use select to clean up auth rule.  Add ScriptError to protect from broken custom rules
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants