Update: deleted since it is now redundant
Update: switch to acts_as_taggable_on_steroids more features, less pain/bugs 🙂
Need simple input/output for tags and got acts_as_taggable_on_steroids ?
…..
and in your forms:
f.text_area('tag_list')
Done!
#Spec:
it "does not create duplicated tags" do
@taggable.tag_list = "Bad, Bad, Evil"
@taggable.save!
@taggable.tags.size.should == 2
end
#Often need count of Tags ?
#taggings.rb
belongs_to :tag, :counter_cache=>'taggings_count'
UPDATE
acts_as_searchable is no longer maintained, please switch over to the new and healthy world of search_do bug-free, clear structure and paginating!
Too many crappy tutorials around, with wrong or only partial information of how to get started. Took me almost 2 hours to get it working, so here comes a short How To/Summary for future reference.
estraier: host: localhost user: admin password: admin port: 1978 node: xx_development
Hope this helps 🙂
# Controller
class UserController < ApplicationController
autocomplete_for :user, :name
end
#Customized....
autocomplete_for :user, :name do |items,method|
render :text => items.map{|item| "#{item.send(method)} -- #{item.id}"}.join("\n")
end
# View
<%= f.text_field :auto_user_name, :class => 'autocomplete', 'autocomplete_url'=>autocomplete_for_user_name_users_path %>
# Routes
map.resources :users, :collection => { :autocomplete_for_user_name => :get}
#JS
#any library you like
#(includes examples for jquery jquery.js + jquery.autocomplete.js + jquery.autocomplete.css )
jQuery(function($){//on document ready
//autocomplete
$('input.autocomplete').each(function(){
var input = $(this);
input.autocomplete(input.attr('autocomplete_url'));
});
});
#Model(input/output association)
class User
find_by_autocomplete('name')
end
class Post
autocomplete_for('user','name') # auto_user_name= + auto_user_name
end
.
Not as thought free as the default version, but gives you a lot more control.
script/plugin install git://github.com/grosser/simple_auto_complete.git
README
Since no one wants to write the documentation, the simplest solution would be to let everyone write documentation, without noticing…
Normal documentation:
An Organisation is a firm or school that has an address(required) and can have users as members.
Pragmatig documentation with examples:
Organisation: - requires an address organisation.address - can have users as members organisation.members << User
Test:
describe Organisation do
it "requires an address" do
@organisation.should_not be_valid?
@organisation.address = Address.new
@organisation.should be_valid
end
it "can have users as members" do
@organisation.should be_valid
@organisation.members << User.new
@organisation.should be_valid
end
end
#before :each omitted
With the help of some spec -f or agiledox magic, we can extract:
An Organisation: - requires an address - can have users as members
looks familliar ?
I prefer this kind of testing, since it does not generate so many 3-liners(2(do/end)+1) nor uses “it should” all the time, which makes it look more documentation-ish.
DISCLAIMER: This way of writing tests is not RSpec-pure in that it does not use ‘it should’ and has more than on assertion (should) per example.
In case of failure the normal should be_redirect and its friends are far from helpful…
expected redirect? to return true, got false expected "new", got nil
Now you can have this:
Status should be redirect but was 200(success)
- rendered addresses/new
- Flash:
:error = Address contains errors!
- Errors:Errors on @address(Address):
City can't be blank
Usage
Install
script/plugin install git://github.com/grosser/rspec_response_enhancer.git add to spec/spec_helper.rb: Spec::Runner.configure do |config| ... config.include(RspecResponseEnhancer) ... end
And as added benefit you no longer need to build should be_success when you already have a should render_template, since render_template now gives detailed error messages!
Michael Grosser, the Blog 