Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in good_practices.md #1679

Merged
merged 1 commit into from
Dec 12, 2024
Merged

Fix typo in good_practices.md #1679

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion wiki/good_practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ ambiguous ("manager") class names.
#### Avoid the injection of data, as opposed to behaviour

Injection of data, as opposed to behaviour, is a subtype of the poltergeist anti-pattern,
with the 'geist in this case being the container. If a class needs to be aware of the current
with the geist in this case being the container. If a class needs to be aware of the current
date and time, you don't inject a DateTime, which is data; instead, you inject an abstraction
over the system clock. This is not only correct for DI; it is absolutely essential for testability,
so that you can test time-varying functions without needing to actually wait on them.
Expand Down
Loading