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

[[FIX]] Remove null value from errors array #3049

Merged
merged 1 commit into from
Oct 18, 2016

Conversation

jugglinmike
Copy link
Member

When reporting unrecoverable errors, JSHint would insert two elements
into the global errors array: a descriptor for the error itself, and a
null value. Because this behavior is undocumented and inconsistent, it
is most likely the result of a programming error. Ensure that the
JSHINT.errors collection contains only error descriptor.


@rwaldron This has been around since the first commit!

}, null);

Funny how the testing infrastructure was built up to tolerate it.

When reporting unrecoverable errors, JSHint would insert two elements
into the global `errors` array: a descriptor for the error itself, and a
`null` value. Because this behavior is undocumented and inconsistent, it
is most likely the result of a programming error. Ensure that the
`JSHINT.errors` collection contains only error descriptor.
@coveralls
Copy link

coveralls commented Oct 18, 2016

Coverage Status

Coverage remained the same at 97.75% when pulling e4bad3b on jugglinmike:remove-null-error into f62dcb7 on jshint:master.

@rwaldron rwaldron merged commit f7eb3d7 into jshint:master Oct 18, 2016
jugglinmike added a commit to jugglinmike/jshint that referenced this pull request Oct 18, 2016
When reporting unrecoverable errors, JSHint would insert two elements
into the global `errors` array: a descriptor for the error itself, and a
`null` value. Because this behavior is undocumented and inconsistent, it
is most likely the result of a programming error. Ensure that the
`JSHINT.errors` collection contains only error descriptor.
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.

None yet

3 participants