Commit e93cffa8 authored by Filipa Lacerda's avatar Filipa Lacerda

Merge branch 'MadLittleMods-master-patch-55656' into 'master'

Fix a couple Vuex typos

See merge request gitlab-org/gitlab-ce!20046
parents 2e71a0e9 dc90eaf1
...@@ -78,7 +78,7 @@ In this file, we will write the actions that will call the respective mutations: ...@@ -78,7 +78,7 @@ In this file, we will write the actions that will call the respective mutations:
```javascript ```javascript
import * as types from './mutation_types'; import * as types from './mutation_types';
import axios from '~/lib/utils/axios-utils'; import axios from '~/lib/utils/axios_utils';
import createFlash from '~/flash'; import createFlash from '~/flash';
export const requestUsers = ({ commit }) => commit(types.REQUEST_USERS); export const requestUsers = ({ commit }) => commit(types.REQUEST_USERS);
...@@ -214,7 +214,7 @@ import { mapGetters } from 'vuex'; ...@@ -214,7 +214,7 @@ import { mapGetters } from 'vuex';
}; };
``` ```
### `mutations_types.js` ### `mutation_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.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment