README.md in effective_logging-2.0.3 vs README.md in effective_logging-2.0.4

- old
+ new

@@ -223,9 +223,17 @@ Each changed attribute will have its before and after values logged to form an activity log. And on each create / destroy / update, a full dump of all current attributes is saved, forming an audit log. +If this ends up hammering your database, you can skip logging the associations by using `except` or `include_associated: false` + +```ruby +class Post < ActiveRecord::Base + log_changes include_associated: false +end +``` + There is some initial support for passing `only`, `except`, and `additionally` to the mixin to customize what attributes are saved. Define your model with `log_changes additionally: [:method1, :method2]` to also _always_ log the value of that method. Even if it's unchanged. Apply your own formatting to the logged title of each attribute by creating an instance method on the resource: