Commit ed3f5ff1 authored by Martin Wortschack's avatar Martin Wortschack

Merge branch 'mw-update-vuex-docs' into 'master'

Update documentation about usage of Vuex

See merge request gitlab-org/gitlab!26580
parents 3429d16c 4c0b6ae7
# Vuex # Vuex
To manage the state of an application you should use [Vuex][vuex-docs]. 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]. _Note:_ All of the below is explained in more detail in the official [Vuex documentation][vuex-docs].
......
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