diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-24 21:09:05 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-24 21:09:05 +0300 |
| commit | c2367afbf57ebc65d5b78a743b5d6a91f0aece9f (patch) | |
| tree | 165c2c54bf72ab3a3a9417d97f63ece5c9eba9f5 /doc/development/module_with_instance_variables.md | |
| parent | 51a9512965d86e3094968fa514e4ae8a96d38cf3 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/module_with_instance_variables.md')
| -rw-r--r-- | doc/development/module_with_instance_variables.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/module_with_instance_variables.md b/doc/development/module_with_instance_variables.md index 1687a9f5ed4..b0eab95190b 100644 --- a/doc/development/module_with_instance_variables.md +++ b/doc/development/module_with_instance_variables.md @@ -30,11 +30,11 @@ People are saying multiple inheritance is bad. Mixing multiple modules with multiple instance variables scattering everywhere suffer from the same issue. The same applies to `ActiveSupport::Concern`. See: [Consider replacing concerns with dedicated classes & composition]( -https://gitlab.com/gitlab-org/gitlab-foss/issues/23786) +https://gitlab.com/gitlab-org/gitlab/issues/16270) There's also a similar idea: [Use decorators and interface segregation to solve overgrowing models problem]( -https://gitlab.com/gitlab-org/gitlab-foss/issues/13484) +https://gitlab.com/gitlab-org/gitlab/issues/14235) Note that `included` doesn't solve the whole issue. They define the dependencies, but they still allow each modules to talk implicitly via the |