소스 검색

update illustration

Evan You 9 년 전
부모
커밋
f2d82c2a1f
4개의 변경된 파일6개의 추가작업 그리고 6개의 파일을 삭제
  1. 4 4
      docs/assets/vuex.ai
  2. 1 1
      docs/en/data-flow.md
  3. 1 1
      docs/en/structure.md
  4. BIN
      docs/en/vuex.png

파일 크기가 너무 크기때문에 변경 상태를 표시하지 않습니다.
+ 4 - 4
docs/assets/vuex.ai


+ 1 - 1
docs/en/data-flow.md

@@ -88,5 +88,5 @@ Here you will notice the component itself is extremely simple: it simply display
 You will also notice the data flow is unidirectional, as it should be in Flux:
 
 <p align="center">
-  <img width="600px" src="https://raw.githubusercontent.com/vuejs/vuex/master/docs/en/vuex.png">
+  <img width="700px" src="vuex.png">
 </p>

+ 1 - 1
docs/en/structure.md

@@ -4,7 +4,7 @@ Vuex doesn't really restrict how you structure your code. Rather, it enforces a
 
 1. Application state lives in a single object.
 2. Only mutation handlers can mutate the state.
-3. Mutations must be synchronous and as simple as possible.
+3. Mutations must be synchronous, and the only side effects they produce should be state mutation.
 4. All asynchronous logic such as data fetching should be performed in actions.
 
 The nice thing about Vuex actions and mutations is that **they are just functions with no external dependencies**. As long as you follow these rules, it's up to you how to structure your project. The simplest Vuex instance can even be declared [in a single file](https://github.com/vuejs/vuex/blob/master/examples/counter/vuex.js)! However, this is unlikely to suffice for any serious project, so here are some recommended structures depending on the scale of your app.

BIN
docs/en/vuex.png


이 변경점에서 너무 많은 파일들이 변경되어 몇몇 파일들은 표시되지 않았습니다.