commit
7066f12d15
|
@ -331,7 +331,7 @@ Alternatively you could store certain metadata for one type of version, and othe
|
|||
You can also specify a custom name for the versions association. This is useful if you already have a `versions` method on your model. For example:
|
||||
|
||||
class Post < ActiveRecord::Base
|
||||
has_paper_trail :versions_association_name => :paper_trail_versions
|
||||
has_paper_trail :versions => :paper_trail_versions
|
||||
|
||||
# Existing versions method. We don't want to clash.
|
||||
def versions
|
||||
|
|
|
@ -18,7 +18,7 @@ module PaperTrail
|
|||
# Values are objects or procs (which are called with `self`, i.e. the model with the paper
|
||||
# trail). See `PaperTrail::Controller.info_for_paper_trail` for how to store data from
|
||||
# the controller.
|
||||
# :versions_association_name the name to use for the versions association. Default is `:versions`.
|
||||
# :versions the name to use for the versions association. Default is `:versions`.
|
||||
def has_paper_trail(options = {})
|
||||
# Lazily include the instance methods so we don't clutter up
|
||||
# any more ActiveRecord models than we have to.
|
||||
|
|
Loading…
Reference in New Issue