diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-19 21:08:23 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-07-19 21:08:23 +0300 |
| commit | 3f0db3db2ad99a74c3969bf2e930814004ccf1ec (patch) | |
| tree | c8b4123b3b4b422b14211430b85556e64eb68a26 /doc/development/module_with_instance_variables.md | |
| parent | 4a721269429a178957e8ce7c6d0a75d3307c9830 (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 f298b603429..0f910f20534 100644 --- a/doc/development/module_with_instance_variables.md +++ b/doc/development/module_with_instance_variables.md @@ -49,9 +49,9 @@ instance variables in the final giant object, and that's where the problem is. ## Solutions We should split the giant object into multiple objects, and they communicate -with each other with the API, i.e. public methods. In short, composition over +with each other with the API, that is, public methods. In short, composition over inheritance. This way, each smaller objects would have their own respective -limited states, i.e. instance variables. If one instance variable goes wrong, +limited states, that is, instance variables. If one instance variable goes wrong, we would be very clear that it's from that single small object, because no one else could be touching it. |