git clone git://github.com/technoweenie/will_paginate.git
take less risky path when monkeypatching named_scope; fix that it no longer requires ActiveRecord::VERSION
use strings in "respond_to?" calls to work around a bug in acts_as_ferret stable (ugh)
add rake release task
add CHANGELOG covering the 2.2.0 release
fix rake manifest
test with rcov and bring it up to 100% test coverage (yeah!!)
rename LinkRenderer#url_params to #url_for and drastically optimize it
added WillPaginate::VERSION
added prev_page/next_page CSS classes on prev/next "buttons" in views
other tests should still run even if the user doesn't have sqlite3
gemify
add Rick Olson to contributors
clean up README; point people to examples/index.html
add examples of pagination links styling
finish transitioning pagination_test.rb to view_test.rb; caught and fixed an edge case in the process
fix view tests for Rails 2.1
big refactoring in view tests; rewrite most of them in much nicer way to test/view_test.rb
fix will_paginate for yet another Rails edge change (r9230)
document WillPaginate.enable_named_scope(false)
remove most of irrelevant named_scope stuff from RDoc
opt-in for named_scope with WillPaginate.enable_named_scope (because of heavy monkeypatching, it's off by default)
crazy monkeypatching to enable named_scope on associations in Rails 1.2.6/2.0.2 ... but finally it works!!
tweak comment for WillPaginate::NamedScope
backport ActiveRecord named_scope from Rails 2.1
assert_queries!
resolve #204 once and for all!
Reduce File.dirname cruft: invoke individual tests with -Ilib:test parameter.
better test for complex page parameter like 'developers[page]'
I don't need Hash#rec_merge, either
Rename LinkRenderer#url_options to `url_params` and refactor it for speed. Closes #197.