Skip to content

Conversation

@Marsup
Copy link
Contributor

@Marsup Marsup commented May 19, 2015

Fixes #361.

@AdriVanHoudt
Copy link
Contributor

maybe add some info in the docs that when linting is enabled it will fail the tests if linting warnings/errors are found

@Marsup
Copy link
Contributor Author

Marsup commented May 19, 2015

Sort of done.

@AdriVanHoudt
Copy link
Contributor

hmm that only suggest that when not provided a value it defaults to 0, it should really say that enabling linting will result in enabling those options

@Marsup
Copy link
Contributor Author

Marsup commented May 19, 2015

That's implied by "defaults to".

@AdriVanHoudt
Copy link
Contributor

I know but it could be read as 'defaults to 0 if the option is used but no value is specified'. Maybe nitpicking but just my thought

@Marsup
Copy link
Contributor Author

Marsup commented May 19, 2015

We'll see if @geek wants a better wording, it's clear enough for me.

@AdriVanHoudt
Copy link
Contributor

👍

@geek geek added the feature New functionality or improvement label May 19, 2015
@geek geek added this to the 5.8.2 milestone May 19, 2015
@geek geek self-assigned this May 19, 2015
geek added a commit that referenced this pull request May 19, 2015
Default both linting thresholds to 0.
@geek geek merged commit b9d95ef into hapijs:master May 19, 2015
@Marsup Marsup deleted the zero-lint branch May 20, 2015 17:58
@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

feature New functionality or improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Lint option -L should fail test if any linting problems are found

3 participants