docs(guides): remove links to deprecated examples #1495
Merged
Conversation
This file contains hidden or 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
The Jest and Mocha examples have been deprecated by the vue-test-utils maintainers. The READMEs in those deprecated examples point to Vue CLI. This commit will update the links to point to the Vue CLI plugins for Jest and Mocha.
|
Great, thanks. We should redo docs - a lot has changed in 2016/2017. |
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.
Description
The Jest and Mocha examples in the docs have been deprecated by the vue-test-utils maintainers. The READMEs in those deprecated examples just point to the Vue CLI website.
This commit will update the URLs in the docs to point to the Vue CLI plugins cli-plugin-unit-jest and cli-plugin-unit-mocha.
Checklist
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch.fix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: