updates for 0.12.9

Author: yyx990803

source/api/directives.md

@@ -61,7 +61,7 @@ Alternatively, you can bind the directive directly to an Object. The keys of the
 
 Internally, {{ Mustache }} interpolations inside attributes are compiled into computed `v-attr` directives.
 
-Starting in 0.12.8, `v-attr` also sets the corresponding property on the element if the property exists. For example, `<input value="{% raw %}{{val}}{% endraw %}">` will not only update the attribute, but also set the value property. If the element doesn't have a corresponding property for the bound attribute, it will not be set.
+Starting in 0.12.8, when used on input elements' `value` attribute, `v-attr` also sets the corresponding `value` property on the element. For example, `<input value="{% raw %}{{val}}{% endraw %}">` will not only update the attribute, but also set the underlying JavaScript property.
 
 <p class="tip">You should use `v-attr` instead of mustache binding when setting the `src` attribute on `<img>` elements. Your templates are parsed by the browser before being compiled by Vue.js, so the mustache binding will cause a 404 when the browser tries to fetch it as the image's URL.</p>
 

source/guide/components.md

@@ -547,7 +547,7 @@ var parent = new Vue({
 
 ## Private Assets
 
-Sometimes a component needs to use assets such as directives, filters and its own child components, but might want to keep these assets encapsulated so the component itself can be reused elsewhere. You can do that using the private assets instantiation options. Private assets will only be accessible by the instances of the owner component and its child components.
+Sometimes a component needs to use assets such as directives, filters and its own child components, but might want to keep these assets encapsulated so the component itself can be reused elsewhere. You can do that using the private assets instantiation options. Private assets will only be accessible by the instances of the owner component, components that inherit from it, and its child components in the view hierarchy.
 
 ``` js
 // All 5 types of assets
@@ -573,6 +573,8 @@ var MyComponent = Vue.extend({
 })
 ```
 
+<p class="tip">You can prohibit child components from accessing a parent component's private assets by setting `Vue.config.strict = true`.</p>
+
 Alternatively, you can add private assets to an existing Component constructor using a chaining API similar to the global asset registration methods:
 
 ``` js
@@ -583,6 +585,40 @@ MyComponent
   // ...
 ```
 
+### Asset Naming Convention
+
+Some assets, such as components and directives, appear in templates in the form of HTML attributes or HTML custom tags. Since HTML attribute names and tag names are **case-insensitive**, we often need to name our assets using dash-case instead of camelCase. **Starting in 0.12.9**, it is now supported to name your assets using camelCase, and use them in templates with dash-case.
+
+**Example**
+
+``` js
+// in a component definition
+components: {
+  // register using camelCase
+  myComponent: { /*... */ }
+}
+```
+
+``` html
+<!-- use dash case in templates -->
+<my-component></my-component>
+```
+
+This works nicely with [ES6 object literal shorthand](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Object_initializer#New_notations_in_ECMAScript_6):
+
+``` js
+import compA from './components/a';
+import compB from './components/b';
+
+export default {
+  components: {
+    // use in templates as <comp-a> and <comp-b>
+    compA,
+    compB
+  }
+}
+```
+
 ## Content Insertion
 
 When creating reusable components, we often need to access and reuse the original content in the hosting element, which are not part of the component (similar to the Angular concept of "transclusion".) Vue.js implements a content insertion mechanism that is compatible with the current Web Components spec draft, using the special `<content>` element to serve as insertion points for the original content.