Skip to content
This repository has been archived by the owner on Jan 5, 2023. It is now read-only.

Commit

Permalink
Merge pull request #3 from Jason-Cooke/patch-1
Browse files Browse the repository at this point in the history
docs: fix typo
  • Loading branch information
jadehopepunk authored Jul 1, 2019
2 parents fcf6b15 + 732fc3a commit 0108725
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,9 @@ application logic.
Entities are the "Data" part of DCI. They represent your Domain models that you probably
want to persist to a data store of some sort. To avoid the sort of complexity that often
occurs in models in Rails apps, Playhouse entities should have no functionality other than
defining their data structure and connecting to the persistance layer.
defining their data structure and connecting to the persistence layer.

Playhouse does not care what persistance library you use. ActiveRecord works fine, just add
Playhouse does not care what persistence library you use. ActiveRecord works fine, just add
the gem to your app and start using it. We recommend you don't use validations (Contexts do
validations in Playhouse), keep relationships to necessary ones only, and don't use scopes
(queries go in Roles).
Expand Down

0 comments on commit 0108725

Please sign in to comment.