mirrors/vue-meta
2
0
Fork 0
mirror of https://github.com/tenrok/vue-meta.git synced 2026-06-17 15:10:34 +03:00
Code Activity

chore: spell & consistency check

Browse Source
This commit is contained in:
pimlie
2019-03-11 12:29:04 +01:00
parent 8024012cf9
commit de68dfcaab
9 changed files with 21 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guide/README.md
+1 -1
View File
@@ -3,7 +3,7 @@
This step is optional if you don't need SSR and `Vue` is available as a global variable. `vue-meta` will install itself in this case.
:::
In order to use this plugin, you first need to pass it to `Vue.use` - if you're not rendering on the server-side, your JS entry file will suffice. If you are rendering on the server, then place it in a file that runs both on the server and on the client before your root instance is mounted. If you're using [`vue-router`](https://github.com/vuejs/vue-router), then your main `router.js` file is a good place:
In order to use this plugin, you first need to pass it to `Vue.use` - if you're not rendering on the server-side, your entry file will suffice. If you are rendering on the server, then place it in a file that runs both on the server and on the client before your root instance is mounted. If you're using [`vue-router`](https://github.com/vuejs/vue-router), then your main `router.js` file is a good place:
**router.js:**
```js
docs/guide/caveats.md
+1 -1
View File
@@ -3,7 +3,7 @@
## Reactive variables in template functions
Both [title](/api/#titletemplate) as [meta](/api/#content-templates) support using template function.
Due to how Vue.js determines reactivity it is not possible to use reactive variables directly in template function
Due to how Vue determines reactivity it is not possible to use reactive variables directly in template function
```js
{
docs/guide/special.md
+3 -3
View File
@@ -14,7 +14,7 @@ With content value we mean the following value of a `metaInfo` property:
- the value of `[contentKeyName]` or `innerHTML` keys for `collection` types as [`meta`](/api/#meta)
:::
The following might be a bit-farfetched, but its just an example
The following might be a bit-far-fetched, but its just an example
```js
// parent
metaInfo: {
@@ -99,10 +99,10 @@ methods: {
## Boolean attributes
`vue-meta` maintains a [list](https://github.com/nuxt/vue-meta/blob/master/src/shared/constants.js) of attributes which are boolean attributes according to the HTML specs (and some extra). Whatever value you will pass to these attributes, they will be rendered as a boolean attribute.<sup>*</sup>
`vue-meta` maintains a [list](https://github.com/nuxt/vue-meta/blob/master/src/shared/constants.js) of attributes which are Boolean attributes according to the HTML specs (and some extra). Whatever value you will pass to these attributes, they will be rendered as a Boolean attribute.<sup>*</sup>
<sup>*</sup><small>Except for the special values `undefined` and `null`, see above</small>
:::tip Note
Prior to `v2.0` any attribute key with `undefined` as value was rendered as boolean attribute. This has been removed as packagers often remove object properties with an `undefined` value as given `a = {}` then `a.a === undefined`
Prior to `v2.0` any attribute key with `undefined` as value was rendered as Boolean attribute. This has been removed as bundlers often remove object properties with an `undefined` value as given `a = {}` then `a.a === undefined`
:::
docs/guide/ssr.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Server Side Rendering
If you have an isomorphic/universal webapp, you'll likely want to render your metadata on the server side as well. Here's how.
If you have an isomorphic/universal web application, you'll likely want to render your metadata on the server side as well. Here's how.
## Add `vue-meta` to the context