Skip to content

Commit 01ea4b9

Browse files
authored
Merge pull request vuejs#222 from vuejs/master
获取官方更新
2 parents 47b7f42 + cd05f51 commit 01ea4b9

File tree

10 files changed

+17
-14
lines changed

10 files changed

+17
-14
lines changed

src/api/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ type: api
4444

4545
The merge strategy receives the value of that option defined on the parent and child instances as the first and second arguments, respectively. The context Vue instance is passed as the third argument.
4646

47-
- **See also**: [Custom Option Merging Strategies](/guide/mixins.html#Custom-Option-Merge-Strategies)
47+
- **See also:** [Custom Option Merging Strategies](/guide/mixins.html#Custom-Option-Merge-Strategies)
4848

4949
### devtools
5050

src/guide/forms.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,9 @@ new Vue({
4343

4444
{% raw %}
4545
<div id="example-textarea" class="demo">
46-
<span>Message is:</span>
47-
<p style="white-space: pre">{{ message }}</p><br>
46+
<span>Multiline message is:</span>
47+
<p style="white-space: pre">{{ message }}</p>
48+
<br>
4849
<textarea v-model="message" placeholder="add multiple lines"></textarea>
4950
</div>
5051
<script>

src/guide/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -296,6 +296,10 @@ Now we can pass the todo into each repeated component using `v-bind`:
296296
</div>
297297
```
298298
``` js
299+
Vue.component('todo-item', {
300+
props: ['todo'],
301+
template: '<li>{{ todo.text }}</li>'
302+
})
299303
var app7 = new Vue({
300304
el: '#app-7',
301305
data: {

src/guide/migration-vuex.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,6 @@ __Vuex 2.0__ is a radical redesign and simplification of the API, for those who
1717

1818
__Vuex 1.0__ is mostly backwards-compatible, so requires very few changes to upgrade. It is recommended for those with large existing codebases or who just want the smoothest possible upgrade path to Vue 2.0. This guide is dedicated to facilitating that process, but only includes migration notes. For the complete usage guide, see [the Vuex 1.0 docs](https://github.com/vuejs/vuex/tree/1.0/docs/en).
1919

20-
<p class="tip">The list of deprecations below should be relatively complete, but the migration helper is still being updated to catch them.</p>
21-
2220
## `store.watch` with String Property Path <sup>deprecated</sup>
2321

2422
`store.watch` now only accept functions. So for example, you would have to replace:

src/guide/reactivity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Reactivity in Depth
33
type: guide
4-
order: 15
4+
order: 12
55
---
66

77
We've covered most of the basics - now it's time to take a deep dive! One of Vue's most distinct features is the unobtrusive reactivity system. Models are just plain JavaScript objects. When you modify them, the view updates. It makes state management very simple and intuitive, but it's also important to understand how it works to avoid some common gotchas. In this section, we are going to dig into some of the lower-level details of Vue's reactivity system.
@@ -55,7 +55,7 @@ There are also a few array-related caveats, which were discussed earlier in the
5555

5656
## Declaring Reactive Properties
5757

58-
Since Vue doesn't allow dynamically adding root-level reactive properties, this means you have to initialize you instances by declaring all root-level reactive data properties upfront, even just with an empty value:
58+
Since Vue doesn't allow dynamically adding root-level reactive properties, you have to initialize Vue instances by declaring all root-level reactive data properties upfront, even just with an empty value:
5959

6060
``` js
6161
var vm = new Vue({

src/guide/render-function.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Render Functions
33
type: guide
4-
order: 14
4+
order: 15
55
---
66

77
## Basics
@@ -160,12 +160,12 @@ One thing to note: similar to how `v-bind:class` and `v-bind:style` have special
160160
nativeOn: {
161161
click: this.nativeClickHandler
162162
},
163-
// Custom directives. Note that the binding's
163+
// Custom directives. Note that the binding's
164164
// oldValue cannot be set, as Vue keeps track
165165
// of it for you.
166166
directives: [
167167
{
168-
name: 'my-custom-directive',
168+
name: 'my-custom-directive',
169169
value: '2'
170170
expression: '1 + 1',
171171
arg: 'foo',

src/guide/transitioning-state.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Transitioning State
33
type: guide
4-
order: 13
4+
order: 14
55
---
66

77
Vue's transition system offers many simple ways to animate entering, leaving, and lists, but what about animating your data itself? For example:

src/guide/transitions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: 'Transition Effects'
33
type: guide
4-
order: 12
4+
order: 13
55
---
66

77
## Overview

src/guide/unit-testing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ order: 23
66

77
## Setup and Tooling
88

9-
Anything compatible with a module-based build system will work, but if you're looking for a specific recommendation, try the [Karma](http://karma-runner.github.io) test runner. It has a lot of community plugins, including support for [Webpack](https://github.com/webpack/karma-webpack) and [Browserify](https://github.com/Nikku/karma-browserify). For detailed setup, please refer to each project's respective documentation, though these example Karma configurations for [Webpack](https://github.com/vuejs/vue-loader-example/blob/master/build/karma.conf.js) and [Browserify](https://github.com/vuejs/vueify-example/blob/master/karma.conf.js) may help you get started.
9+
Anything compatible with a module-based build system will work, but if you're looking for a specific recommendation, try the [Karma](http://karma-runner.github.io) test runner. It has a lot of community plugins, including support for [Webpack](https://github.com/webpack/karma-webpack) and [Browserify](https://github.com/Nikku/karma-browserify). For detailed setup, please refer to each project's respective documentation, though these example Karma configurations for [Webpack](https://github.com/vuejs-templates/webpack/blob/master/template/test/unit/karma.conf.js) and [Browserify](https://github.com/vuejs-templates/browserify/blob/master/template/karma.conf.js) may help you get started.
1010

1111
## Simple Assertions
1212

themes/vue/layout/partials/sidebar.ejs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@
2424
<% if (fileName === 'installation') { %>
2525
<li><h3>Essentials</h3></li>
2626
<% } %>
27-
<% if (fileName === 'transitions') { %>
27+
<% if (fileName === 'reactivity') { %>
2828
<li><h3>Advanced</h3></li>
2929
<% } %>
3030
<% if (fileName === 'migration') { %>

0 commit comments

Comments
 (0)