Add a note about the hydrating argument of $mount, fixes #193 (#194)

chrisvfritz · web-flow · commit 8706490efc15 · 2018-08-01T15:51:07.000+02:00
Does this make sense? 😄
diff --git a/docs/guide/hydration.md b/docs/guide/hydration.md
@@ -13,12 +13,19 @@ Since the server has already rendered the markup, we obviously do not want to th
 
 If you inspect the server-rendered output, you will notice that the app's root element has had a special attribute added:
 
-``` js
+``` html
 <div id="app" data-server-rendered="true">
 ```
 
 The `data-server-rendered` special attribute lets the client-side Vue know that the markup is rendered by the server and it should mount in hydration mode. Note that it didn't add `id="app"`, just the `data-server-rendered` attribute: you need to add the ID or some other selector to the app's root element yourself or the app won't hydrate properly.
 
+Note that on elements without the `data-server-rendered` attribute, hydration can also be forced by passing `true` to the `hydrating` argument of `$mount`:
+
+``` js
+// Force hydration of the app
+app.$mount('#app', true)
+```
+
 In development mode, Vue will assert the client-side generated virtual DOM tree matches the DOM structure rendered from the server. If there is a mismatch, it will bail hydration, discard existing DOM and render from scratch. **In production mode, this assertion is disabled for maximum performance.**
 
 ### Hydration Caveats
