Skip to content

Commit 159a614

Browse files
committed
readme.md: update links to docs
1 parent e3f3382 commit 159a614

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,21 +15,21 @@ A Vue project with minimal setup and dependencies for trying out [Vetur](https:/
1515
Try all features below in `src/Test.vue`. You can read more about these features in Vetur's documentation: https://vuejs.github.io/vetur/.
1616

1717
- Do an emmet expansion on the html template. For example, type `div` and then tab.
18-
- Complete on `<router|`. Because of the [`vue-router`](https://router.vuejs.org/) dependency, you should see [`router-link`](https://router.vuejs.org/api/#router-link). Read more about this feature in [Framework Support](https://vuejs.github.io/vetur/framework.html).
19-
- `yarn add element-ui`, reload the project and complete `<el`. You should see all tags from [Element UI](https://element.eleme.cn/#/en-US/component). Read more about this feature in [Framework Support](https://vuejs.github.io/vetur/framework.html).
20-
- Complete on `<foo`. You should see `<foo-tag>`. Read more about this feature in [Framework Support](https://vuejs.github.io/vetur/framework.html).
18+
- Complete on `<router|`. Because of the [`vue-router`](https://router.vuejs.org/) dependency, you should see [`router-link`](https://router.vuejs.org/api/#router-link). Read more about this feature in the [Supported Frameworks](https://vuejs.github.io/vetur/guide/component-data.html#supported-frameworks) section.
19+
- `yarn add element-ui`, reload the project and complete `<el`. You should see all tags from [Element UI](https://element.eleme.cn/#/en-US/component). Read more about this feature in the [Supported Frameworks](https://vuejs.github.io/vetur/guide/component-data.html#supported-frameworks) section.
20+
- Complete on `<foo`. You should see `<foo-tag>`. Read more about this feature in the [Workspace Component](https://vuejs.github.io/vetur/guide/component-data.html#workspace-component-data) section.
2121
- Hover over any tags such as `<div>` or `<router-link>`. You'll see the tag's description.
2222
- Because of `"vetur.experimental.templateInterpolationService": true` in `.vscode/settings.json`, you should see an error on `{{ fo }}` in the template section. Change it to `foo` to fix the error.
2323
- Delete the `foo` in `{{ foo }}`. Type `b`. You should see completion of `bar`.
2424
- In script section, try `_.`. You should see all [lodash](https://lodash.com)'s methods.
2525
- Install another library with types, such as [jquery](https://api.jquery.com/). `yarn add -S jquery && yarn add -D @types/jquery`. After importing it with `import * as $ from 'jquery'`, you should get `$.` completions.
2626
- Setup [eslint-plugin-vue](https://eslint.vuejs.org/user-guide/) with a `.eslintrc`. Set `"vetur.validation.template": false` to turn off Vetur's builtin ESLint linter. You'll get ESLint warnings now.
2727
- In `<script>` section, add `//@ts-check`. Write some type-unsafe code, such as `let a = 'a'; a = 5`. You'll see an error.
28-
- F1 -> Format the document. You can [configure](https://vuejs.github.io/vetur/formatting.html) the formatters and their settings as well.
28+
- F1 -> Format the document. You can [configure](https://vuejs.github.io/vetur/guide/formatting.html) the formatters and their settings as well.
2929
- In `.prettierrc.json`, set `"singleQuote": true` and format again.
30-
- Type `<style scss` and tab to choose a snippet. You should get a SCSS section setup. These snippets are [customizable](https://vuejs.github.io/vetur/snippet.html).
30+
- Type `<style scss` and tab to choose a snippet. You should get a SCSS section setup. These snippets are [customizable](https://vuejs.github.io/vetur/guide/snippet.html).
3131
- Try some CSS completions in the `<style lang="scss">` section.
32-
- Make some errors in the Vue file and run [vti](https://vuejs.github.io/vetur/vti.html) — you should see all diagnostics printed on CLI.
32+
- Make some errors in the Vue file and run [vti](https://vuejs.github.io/vetur/guide/vti.html) — you should see all diagnostics printed on CLI.
3333

3434
## Next
3535

0 commit comments

Comments
 (0)