Commit 0c652914 authored by Evan Read's avatar Evan Read

Merge branch 'docs-fix-doc-lint-script' into 'master'

Fix docs-lint job that was missing half the docs

See merge request gitlab-org/gitlab!26951
parents 31f71291 01e8498f
...@@ -3,12 +3,12 @@ ...@@ -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. 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: Vuex should be strongly considered when:
- You expect multiple parts of the application to react to state changes - You expect multiple parts of the application to react to state changes
- There's a need to share data between multiple components - There's a need to share data between multiple components
- There are complex interactions with Backend, e.g. multiple API calls - 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) - 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].
## Separation of concerns ## Separation of concerns
......
...@@ -64,7 +64,6 @@ Another example of GitLab as a company would be the following: ...@@ -64,7 +64,6 @@ Another example of GitLab as a company would be the following:
--- ---
When performing actions such as transferring or importing a project between When performing actions such as transferring or importing a project between
subgroups, the behavior is the same as when performing these actions at the subgroups, the behavior is the same as when performing these actions at the
`group/project` level. `group/project` level.
......
...@@ -48,7 +48,7 @@ then ...@@ -48,7 +48,7 @@ then
exit 1 exit 1
fi fi
MD_DOC_PATH=${MD_DOC_PATH:-doc/**/*.md} MD_DOC_PATH=${MD_DOC_PATH:-doc}
function run_locally_or_in_docker() { function run_locally_or_in_docker() {
local cmd=$1 local cmd=$1
......
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