-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Mocha constructor: some fixes and cleanup #4004
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
juergba
added
type: bug
a defect, confirmed by a maintainer
semver-major
implementation requires increase of "major" version number; "breaking changes"
labels
Aug 28, 2019
juergba
force-pushed
the
juergba/mocha-constructor
branch
4 times, most recently
from
August 30, 2019 13:06
2068424
to
897b917
Compare
juergba
force-pushed
the
juergba/mocha-constructor
branch
from
September 10, 2019 13:40
897b917
to
4c40c8a
Compare
I will merge this PR within the next few days. |
craigtaub
reviewed
Sep 20, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All LGTM, think missing doc updates tho.
juergba
force-pushed
the
juergba/mocha-constructor
branch
from
September 21, 2019 06:44
4c40c8a
to
32d0106
Compare
craigtaub
approved these changes
Sep 21, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
holm
pushed a commit
to peakon/mocha
that referenced
this pull request
Jan 14, 2020
In mochajs#4004 there was a change to use the documented `reporterOption` in favour of the setting that had always been used in practice called `reporterOptions`. This broke a lot of configurations that used the `reporterOptions`, which was the only way it every worked AFAIK. This changes the documentation to specify `reporterOptions` instead and ensure that any one that has switched to `reporterOption` after upgrade, still works.
holm
pushed a commit
to peakon/mocha
that referenced
this pull request
Jan 19, 2020
In mochajs#4004 there was a change to use the documented `reporterOption` in favour of the setting that had always been used in practice called `reporterOptions`. This broke a lot of configurations that used the `reporterOptions`, which was the only way it every worked AFAIK. This changes the documentation to specify `reporterOptions` instead and ensure that any one that has switched to `reporterOption` after upgrade, still works.
holm
pushed a commit
to peakon/mocha
that referenced
this pull request
Jan 19, 2020
In mochajs#4004 there was a change to use the documented `reporterOption` in favour of the setting that had always been used in practice called `reporterOptions`. This broke a lot of configurations that used the `reporterOptions`, which was the only way it every worked AFAIK. This changes the documentation to specify `reporterOptions` instead and ensure that any one that has switched to `reporterOption` after upgrade, still works.
holm
pushed a commit
to peakon/mocha
that referenced
this pull request
Jan 20, 2020
In mochajs#4004 there was a change to use the documented `reporterOption` in favour of the setting that had always been used in practice called `reporterOptions`. This broke a lot of configurations that used the `reporterOptions`, which was the only way it every worked AFAIK. This changes the documentation to specify `reporterOptions` instead and ensure that any one that has switched to `reporterOption` after upgrade, still works.
76 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
semver-major
implementation requires increase of "major" version number; "breaking changes"
type: bug
a defect, confirmed by a maintainer
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When Mocha is launched via CLI a whole bunch of options is dumped into the
mocha
instance, like canonical / canonical camel-cased / alias / alias camel-cased versions of option names. This is prone to errors, but not part of this PR ==> see #4011.When the user manually calls the
Mocha
constructor, there are some bugs to be fixed.Furthermore we remove two deprecated options.
Description of the Change
enableTimeouts
optionuseColors
optionignoreLeaks
option: this option does not exist and is redundant tocheckLeaks
inlineDiffs
option:useInlineDiffs
does not existdiff
option:hideDiff
does not existreporterOption
option: its aliasreporterOptions
was processed insteadfullTrace
:fullStackTrace
does not existglobal
option: no alias processingThis is a breaking change.