kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

FE Docs: Fix header hierarchy in Vuex section of Vue.md

Browse source
This commit is contained in:
Dennis Tang 2018-04-16 20:39:58 +00:00
parent 08083f43cb
commit 05375ee689
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/development/fe_guide/vue.md
View file

@ -523,7 +523,7 @@ export default new Vuex.Store({
``` ```
_Note:_ If the state of the application is too complex, an individual file for the state may be better. _Note:_ If the state of the application is too complex, an individual file for the state may be better.
#### `actions.js` ##### `actions.js`
An action commits a mutatation. In this file, we will write the actions that will call the respective mutation: An action commits a mutatation. In this file, we will write the actions that will call the respective mutation:
```javascript ```javascript
@ -550,7 +550,7 @@ import { mapActions } from 'vuex';
}; };
``` ```
#### `getters.js` ##### `getters.js`
Sometimes we may need to get derived state based on store state, like filtering for a specific prop. This can be done through the `getters`: Sometimes we may need to get derived state based on store state, like filtering for a specific prop. This can be done through the `getters`:
```javascript ```javascript
@ -573,7 +573,7 @@ import { mapGetters } from 'vuex';
}; };
``` ```
#### `mutations.js` ##### `mutations.js`
The only way to actually change state in a Vuex store is by committing a mutation. The only way to actually change state in a Vuex store is by committing a mutation.
```javascript ```javascript
@ -586,7 +586,7 @@ The only way to actually change state in a Vuex store is by committing a mutatio
}; };
``` ```
#### `mutations_types.js` ##### `mutations_types.js`
From [vuex mutations docs][vuex-mutations]: From [vuex mutations docs][vuex-mutations]:
> It is a commonly seen pattern to use constants for mutation types in various Flux implementations. This allows the code to take advantage of tooling like linters, and putting all constants in a single file allows your collaborators to get an at-a-glance view of what mutations are possible in the entire application. > It is a commonly seen pattern to use constants for mutation types in various Flux implementations. This allows the code to take advantage of tooling like linters, and putting all constants in a single file allows your collaborators to get an at-a-glance view of what mutations are possible in the entire application.