Browse files

* Add in scope_procedure as an alias for alias_scope.

  • Loading branch information...
1 parent 1ed8434 commit 1280867457d0dc09f6f49200980974808246ed1a @binarylogic committed Aug 26, 2009
Showing with 20 additions and 0 deletions.
  1. +5 −0 CHANGELOG.rdoc
  2. +14 −0 README.rdoc
  3. +1 −0 lib/searchlogic/named_scopes/alias_scope.rb
@@ -1,3 +1,8 @@
+== 2.3.2 relased 2009-08-26
+* Add in scope_procedure as an alias for alias_scope.
+* Fixed bug with not_blank condition.
== 2.3.1 released 2009-08-24
* Added blank and not_blank conditions.
@@ -170,6 +170,18 @@ You can do:
Again, these just map to named scopes. Use Searchlogic's dynamic scopes, use scopes on associations, use your own custom scopes. As long as it maps to a named scope it will join the conditions with 'OR'. There are no limitations.
+== Create scope procedures
+Sometimes you notice a pattern in your application where you are constantly combining certain named scopes. You want to keep the flexibility of being able to mix and match small named scopes, while at the same time being able to call a single scope for a common task. User searchlogic's scpe procedure:
+ User.scope_procedure :awesome, lambda { first_name_begins_with("ben").last_name_begins_with("johnson").website_equals("") }
+All that this is doing is creating a class level method, but what is nice about this method is that is more inline with your other named scopes. It also tells searchlogic that this method is 'safe' to use when using the search method. Ex:
+ => true)
+Otherwise searchlogic will ignore the 'awesome' condition because there is no way to tell that its a valid scope. This is a security measure to keep users from passing in a scope with a named like 'destroy_all'.
== Make searching and ordering data in your application trivial
The above is great, but what about tying all of this in with a search form in your application? What would be really nice is if we could use an object that represented a single search. Like this...
@@ -274,6 +286,8 @@ Before I use a library in my application I like to glance at the source and try
Searchlogic utilizes method_missing to create all of these named scopes. When it hits method_missing it creates a named scope to ensure it will never hit method missing for that named scope again. Sort of a caching mechanism. It works in the same fashion as ActiveRecord's "find_by_*" methods. This way only the named scopes you need are created and nothing more.
+The search object is just a proxy to your model that only delegates calls that map to named scopes and nothing more. This is obviously done for security reasons. It also helps make form integration easier, by type casting values, and playing nice with form_for. This class is pretty simple as well.
That's about it, the named scope options are pretty bare bones and created just like you would manually.
== Credit
@@ -44,6 +44,7 @@ def alias_scope(name, options = nil)
+ alias_method :scope_procedure, :alias_scope
def alias_scopes # :nodoc:
@alias_scopes ||= {}

0 comments on commit 1280867

Please sign in to comment.