Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Relocated paragraph to later step in the README

  • Loading branch information...
commit 361f84fd89ccd9803fecd07e360157028e9cb288 1 parent 58c303f
Evan Light authored March 15, 2013

Showing 1 changed file with 2 additions and 3 deletions. Show diff stats Hide diff stats

  1. 5  README.md
5  README.md
Source Rendered
@@ -62,9 +62,6 @@ end
62 62
 
63 63
 Fields and associations on the Domain Model are determined via ActiveRecord reflection.  The Domain Model is coupled to its ActiveRecord class by naming convention.
64 64
 
65  
-Domain Model classes should share the same name as the AR classes except they should not end in "Data".  So OrderData < ActiveRecord::Base maps to the Order domain 
66  
-model class.
67  
-
68 65
 Be aware that your Domain Model test/specs will need to stub/mock out dependencies upon their Repository and other Domain Model objects.  That is, you Domain Model instances will lack fields or associations in their tests. This is because Domain Model objects are [POROs](http://blog.jayfields.com/2007/10/ruby-poro.html) until they are registered with edr at runtime.  As you should not want to test the framework, this should facilitate testing your Domain Model and your persistence in isolation from one another and from the edr framework.
69 66
 
70 67
 ``` ruby
@@ -80,6 +77,8 @@ end
80 77
 
81 78
 ## STEP3: map data objects to domain objects
82 79
 
  80
+Domain Model classes should share the same name as the AR classes except they should not end in "Data".  So OrderData < ActiveRecord::Base maps to the Order domain model class.
  81
+
83 82
 You probably want the below in a <code>config/initializers/edr.rb</code>
84 83
 
85 84
 ``` ruby

0 notes on commit 361f84f

Please sign in to comment.
Something went wrong with that request. Please try again.