diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-11 09:10:11 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-11 09:10:11 +0300 |
| commit | 65a1175e466105fca1f40cb5a995fdb100ff334e (patch) | |
| tree | 562573b4fc7a0cd748d07d6a1720b4b13d36386a /doc/development/fe_guide | |
| parent | 3a52deac114dda8a1ee0da597c148b0dfc5dcf35 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/fe_guide')
| -rw-r--r-- | doc/development/fe_guide/vuex.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/fe_guide/vuex.md b/doc/development/fe_guide/vuex.md index b69bbb8b527..675f30feba6 100644 --- a/doc/development/fe_guide/vuex.md +++ b/doc/development/fe_guide/vuex.md @@ -3,12 +3,12 @@ When there's a clear benefit to separating state management from components (e.g. due to state complexity) we recommend using [Vuex][vuex-docs] over any other Flux pattern. Otherwise, feel free to manage state within the components. Vuex should be strongly considered when: + - You expect multiple parts of the application to react to state changes - There's a need to share data between multiple components - There are complex interactions with Backend, e.g. multiple API calls - The app involves interacting with backend via both traditional REST API and GraphQL (especially when moving the REST API over to GraphQL is a pending backend task) - _Note:_ All of the below is explained in more detail in the official [Vuex documentation][vuex-docs]. ## Separation of concerns |