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

docs: attr is data-vmid not just vmid (#519)

Browse Source 
Actual output is data-vmid
This commit is contained in:
719media
2020-02-23 06:48:28 -08:00
committed by GitHub
parent a94b2bc589
commit 9655a81a8a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/faq/README.md
+1 -1
View File
@@ -70,7 +70,7 @@ This is not what we want, since the meta `description` needs to be unique for ev
**Output:** **Output:**
```html ```html
<meta charset="utf-8"> <meta charset="utf-8">
<meta vmid="description" name="description" content="bar"> <meta data-vmid="description" name="description" content="bar">
``` ```
While solutions like `react-helmet` manage the occurrence order and merge behaviour for you automatically, it involves a lot more code and is therefore prone to failure in some edge-cases, whereas this method is _almost_ bulletproof because of its versatility; _at the expense of one tradeoff:_ these `vmid` properties will be rendered out in the final markup (`vue-meta` uses these client-side to prevent duplicating or overriding markup). If you are serving your content gzipped, then the slight increase in HTTP payload size is negligible. While solutions like `react-helmet` manage the occurrence order and merge behaviour for you automatically, it involves a lot more code and is therefore prone to failure in some edge-cases, whereas this method is _almost_ bulletproof because of its versatility; _at the expense of one tradeoff:_ these `vmid` properties will be rendered out in the final markup (`vue-meta` uses these client-side to prevent duplicating or overriding markup). If you are serving your content gzipped, then the slight increase in HTTP payload size is negligible.