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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Final 3.0 CLI touches #334

Merged
merged 1 commit into from Feb 8, 2017
Merged

Final 3.0 CLI touches #334

merged 1 commit into from Feb 8, 2017

Conversation

jwilsson
Copy link
Member

@jwilsson jwilsson commented Feb 3, 2017

Which issue, if any, does this resolve?
#321 among others.

Is there anything in this PR that needs extra explaining or should something specific be focused on?
@kokarn Is this what you had in mind? Hope I didn't step on any toes 馃槵

* Reject Runner with real Errors.
* Fix handling of --max-warnings=-1. Closes #321.
* Fix a minor refactor typo with custom linters.
Copy link
Member

@kokarn kokarn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, not stepping on my toes at all. Especially when I'm so damn slow 馃拑

status: EXIT_CODES.WARNING
});
return reject(new RunnerError(
'',
Copy link
Member

@kokarn kokarn Feb 6, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't we avoid this empty message somehow?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you suggesting we put a message there? Or something else?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what to do, just don't like passing empty messages I guess.
Can't we have a default just to ease my mind or will that break something?

I guess it's stuff like if( error.message ) that scares me a bit.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't wanna unnecessary output in case someone's piping the output somewhere else, reporters will already have printed everything that's needed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I guess that makes sense. Just leaves me with a funny feeling.

@jwilsson jwilsson merged commit f8473d1 into master Feb 8, 2017
@jwilsson jwilsson deleted the final-cli-touches branch February 8, 2017 18:08
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

Successfully merging this pull request may close these issues.

Max-Warnings Config Issue
2 participants