Skip to content

WorkflowGuidelines: clarify Primitive Obsession #102

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

Closed
parhamsaremi wants to merge 1 commit into from
Closed

WorkflowGuidelines: clarify Primitive Obsession #102

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 WorkflowGuidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@

* Primitive Obsession:

Primitive Obsession is a situation where simple data types such as strings, integers, or arrays are overused in place of more appropriate objects.
Primitive Obsession is a situation where simple data types such as strings, integers, or arrays are overused in place of more appropriate objects. Using primitives is bad because they can't contain any model-specific logic or behaviour. Also, they lose their type safety. A string is a string. It doesn't matter if it's a name, a phone number, or a password. This makes it easy to make mistakes and hard to understand the code.

Example:
```
Expand Down