V11 (Major) #509
Merged
V11 (Major) #509
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
…cludeNonEnumerableProperties"" This reverts commit aeac1ef.
…5.5.0' into v11 * remotes/origin/depfu/update/npm/eslint-5.5.0: Update eslint to version 5.5.0
….2.0' into v11 * remotes/origin/depfu/update/npm/mocha-5.2.0: Upgrade mocha to version 5.2.0
…0.65.1' into v11 * remotes/origin/depfu/update/npm/rollup-0.65.1: Update rollup to version 0.65.1
…0.1' into v11 * remotes/origin/depfu/update/npm/nyc-13.0.1: Update nyc to version 13.0.1
…config-pretty-standard-2.0.0' into v11 * remotes/origin/depfu/update/npm/eslint-config-pretty-standard-2.0.0: Upgrade eslint-config-pretty-standard to version 2.0.0
The diff method used to return { inline: <boolean>, diff: <magicPen> },
but that was changed in e22bdef with a backwards compatibility hack
that installed a self-referencing 'diff' property.
I suggest we remove the backwards compatibility in Unexpected 11.
…glify-5.0.2' into v11 * origin/depfu/update/npm/rollup-plugin-uglify-5.0.2: Update rollup-plugin-uglify to version 5.0.2
…thOldDiffResults Drop compatibility with pre-10.10.0 type.diff return values
Fixes tests in node versions that are using the transpiled version.
…site when doing releases
Include a link to the migration guide.
Made all internal doc URL's relative and with a trailing slash
…calBrowser Fix test script to execute headless browser in place of phantomjs.
* master: Avoid http redirects in assets linked from the frontpage Don't let changes to expect.output.preferredWidth propagate into existing clones Remove unused variable Simplify to call the callback with error Simplify to be rejected with
Remove support for expect.async
…ions Remove long-deprecated support for this.subject etc. in assertion handlers
* master: Update unexpected-documentation-site-generator to version 5.1.0 Update rollup to version 1.0.1
* docs/migrationGuide: Tweak a section heading. Mention the two additional deprecations on the release and migration pages Fix typos Add a separate releases page with an entry for 11.0.0 Stop generating a menu entry for the migration page Show the expect.it() function argument syntax. Add a function by value example. Convert all assertion references to links. Fix rendering the hyphen. Correct misspellings. Reorder the sections within the migration guide. Clarify the functions by value section. Swap "Use of" to "Using" to differentiate the intent. Tighten the examples and emphasise expect.it(). Minor copy edits to tighten the language. Add an initial migration guide.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Breaking changes
Please see the migration guide.
require('unexpected')Freeze the top-level expect #517expect.asyncRemove support for expect.async #566this.subjectetc. in assertion handlers Remove long-deprecated support for this.subject etc. in assertion handlers #567Check plugin compatibility
TODO after merging v11 into master: