You can clone with
HTTPS or Subversion.
Documented the correct way to get TimelineFu in your project
Merge pull request #4 from cs/master
Support for passing lambdas to `fires` as :actor, :secondary_subject and :subject
add support to pass lambda's to `fires` for subject, secondary_subjec…
…t and actor.
add rails 3 generator
Regenerated gemspec for version 0.3.0
Version bump to 0.3.0
Added support for specifying multiple events to fire, e.g. "fires :ne…
…w_comment, :on => [:create, :update]"
Regenerated gemspec for version 0.2.0
Version bump to 0.2.0
Added matchers/macros for testing.
Minor refactoring to reduce duplication
New test to allow the secondary subject to be self
Regenerated gemspec for version 0.1.1
Version bump to 0.1.1
Visual tweaks. Aaaaalways visual tweaks
Visual tweaks. Always visual tweaks
Oops, rdoc lists < markdown lists
Oh, and one last thing...
Big rewrite of README
Minor readability tweak
Missed a rename for the generator
Make timeline_fu into a gem
Add a test for the ArgumentException
Remove overkill exception
In tests, add comments on lists to test :secondary_subject
Obliterate has_timeline from the surface of the planet
Unfortunately, thanks to git, it'll still be observable beneath the surface
secondary_actor => secondary_subject
Make rdoc without changing anything else
Create generator for the TimelineEvent class and its migration
Rename the concepts around TimelineEvents:
- event_type remains the same
- 'subject' defaults to the instance that had a 'fires' triggered
- actor and secondary_actor are two spots where you can cram people