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(reporters): Revert the backwards-incompatible log priority order changes #2676

Merged
merged 2 commits into from
Apr 28, 2017

Conversation

mgol
Copy link
Contributor

@mgol mgol commented Apr 26, 2017

Commit 35965d9 changed the order of log priorities, making lots of
configurations no longer print console.log messages. This was a
backwards-incompatible change which this commit reverts.

Tests were added to ensure the proper order is respected.

Fixes #2582


Also, another commit in this PR:

test(reporters): Fix the log suppressing tests

The tests ensuring a lower priority doesn't get logged were written in an
incorrect format so even changing the order in the LOG_PRIORITIES array
would not make them fail.

The tests ensuring a lower priority doesn't get logged were written in an
incorrect format so even changing the order in the LOG_PRIORITIES array
would not make them fail.
…changes

Commit 35965d9 changed the order of log priorities, making lots of
configurations no longer print console.log messages. This was a
backwards-incompatible change which this commit reverts.

Tests were added to ensure the proper order is respected.

Fixes karma-runner#2582
mgol referenced this pull request Apr 26, 2017
Additional fix to the bug, "filter browser logging by level" ([35965d9](35965d9)), closes [#2228](#2228)

Otherwise console.log ignore doesn't work with 
```
browserConsoleLogOptions: {
  level: 'debug',
  terminal: true
}
```
@blackswanny
Copy link
Contributor

according to Mozilla this is the right place for LOG, but people misuse it
https://developer.mozilla.org/en-US/Add-ons/SDK/Tools/console#Setting_the_Logging_Level

@mgol
Copy link
Contributor Author

mgol commented Apr 26, 2017

@blackswanny Regardless what's the correct way spec-wise this was a breaking change which shouldn't happen before 2.0. This PR restores backwards compatibility.

@dignifiedquire dignifiedquire merged commit e93d1e3 into karma-runner:master Apr 28, 2017
@dignifiedquire
Copy link
Member

Thank you @maksimr

@mgol
Copy link
Contributor Author

mgol commented May 5, 2017

@dignifiedquire could you release a new version to npm?

@mgol mgol deleted the log-order-fixes branch May 5, 2017 08:35
@dignifiedquire
Copy link
Member

yeah sorry will do today

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.

3 participants