README.markdown in sluggable_finder-2.3.1 vs README.markdown in sluggable_finder-2.3.2

- old
+ new

@@ -18,19 +18,20 @@ ## FEATURES/PROBLEMS: Slugs are created when a model is created. Subsequent changes to the source field will not modify the slug unless you specifically change the value of the slug field. This is because permalinks should never change. -Complete specs. To test, make sure you create an empty SQLite database file in spec/db/test.db +Complete specs. To test, make sure you create an empty SQLite database. -Then run the following to load the test schema: +Run the following to load the test schema: -rake db:create + rake db:create -Note: I'm using mysql for now due to an apparent bug in ActiveRecord's sqlite3 adapter. -Look for configuration in spec/sluggable_finder_spec.rb +Now you can run the tests + rake spec + ## SYNOPSIS: ### Models class Category < ActiveRecord::Base has_many :posts @@ -67,10 +68,10 @@ class Comment < ActiveRecord::Base sluggable_finder :title, :allow_integer_ids => false end -### Single Table Inheritance (STI) +<h3 id="sti">Single Table Inheritance (STI)</h3> Slug uniqueness will be checked accross all classes in STI models. If you want to scope by sub-class, use :ignore_sti class Comment < SomeParentClass sluggable_finder :title, :ignore_sti => true \ No newline at end of file