diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-19 12:08:42 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-19 12:08:42 +0300 |
| commit | b76ae638462ab0f673e5915986070518dd3f9ad3 (patch) | |
| tree | bdab0533383b52873be0ec0eb4d3c66598ff8b91 /doc/development/directory_structure.md | |
| parent | 434373eabe7b4be9593d18a585fb763f1e5f1a6f (diff) | |
Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42
Diffstat (limited to 'doc/development/directory_structure.md')
| -rw-r--r-- | doc/development/directory_structure.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/directory_structure.md b/doc/development/directory_structure.md index c96e2cc3254..8ba77bade2c 100644 --- a/doc/development/directory_structure.md +++ b/doc/development/directory_structure.md @@ -72,7 +72,7 @@ could make them shallow and more coupled with other contexts. Bounded contexts (or top-level namespaces) can be seen as macro-components in the overall app. Good bounded contexts should be [deep](https://medium.com/@nakabonne/depth-of-module-f62dac3c2fdb) so consider having nested namespaces to further break down complex parts of the domain. -E.g. `Ci::Config::`. +For example, `Ci::Config::`. For example, instead of having separate and granular bounded contexts like: `ContainerScanning::`, `ContainerHostSecurity::`, `ContainerNetworkSecurity::`, we could have: |