kotovalexarian-likes-github
/
paper-trail-gem--paper_trail
mirror of https://github.com/paper-trail-gem/paper_trail.git
1
0
Fork 0
Code Releases Activity

updated readme

This commit is contained in:
Ninigi 2015-09-23 14:53:01 +02:00
parent baca9b0557
commit 02b1c09e3e
1 changed files with 6 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -332,27 +332,22 @@ a.versions.last.event # 'update'
You can also use the corresponding callback-methods seperately instead of using
the :on option. If you choose to use the callback-methods, PaperTrail will only
track the according events - so `paper_trail_create` is basically the same as
track the according events - so `paper_trail_on_create` is basically the same as
`has_paper_trail :on => :create`.
```ruby
class Article < ActiveRecord::Base
paper_trail_destroy
# or paper_trail_after_destroy
# paper_trail_destroy(:before) will create the version before the actual
# destroy event
paper_trail_update
paper_trail_create
has_paper_trail
paper_trail_on_destroy
paper_trail_on_update
paper_trail_on_create
end
```
The `paper_trail_destroy` method can be configured to be called `:before` or `:after` the
destroy event. This can be usefull if you are using a third party tool that alters the
destroy method (for example paranoia). If you do not pass an argument, it will default
to after_destroy.
`paper_trail_after_destroy` and `paper_trail_before_destroy` are alias methods for
`paper_trail_destroy(:before/:after)`.
to after_destroy.
## Choosing When To Save New Versions