diff options
| author | Xavier Noria <fxn@hashref.com> | 2015-02-06 10:22:53 +0100 |
|---|---|---|
| committer | Xavier Noria <fxn@hashref.com> | 2015-02-06 10:29:05 +0100 |
| commit | 6f8d9bd6da6349d3d179f2e72db5bc7044a8e5c1 (patch) | |
| tree | 9d935cb48f5b8b1eff8b21b61bd932a5b48a7951 /guides/source/configuring.md | |
| parent | a2af7bb9280f2b52da0f8af3796fbe2e388025ff (diff) | |
| download | rails-6f8d9bd6da6349d3d179f2e72db5bc7044a8e5c1.tar.gz rails-6f8d9bd6da6349d3d179f2e72db5bc7044a8e5c1.tar.bz2 rails-6f8d9bd6da6349d3d179f2e72db5bc7044a8e5c1.zip | |
revises AM:Dirty example [Godfrey Chan & Xavier Noria]
The existing example seems somewhat forced: is it realistic
to have a model that accepts state in its initializer but
considers it has not been changed? By allowing state changes
to happen only via accessors it seems more natural that new
instances are considered to be unchanged (as they are in AR).
[ci skip]
Diffstat (limited to 'guides/source/configuring.md')
0 files changed, 0 insertions, 0 deletions