Dante Soares
Dante Soares
I would say just allow voting on the questions themselves (not the question_part objects) if they are published. You would have to change the multipart UI to make this easier...
It seems to be complaining about the validation: validates_uniqueness_of :user_id, :scope => :votable_id in vote.rb We probably want to keep this validation (one vote per user per votable), so if...
The vote methods are supposed to automatically update any existing votes when used or create a new vote if it doesnt exist. So it's strange that the vote created that...
Validation occurs in the model, so unit tests should test that. You can't test how a view "looks" in a test, but you can test that it renders at all...
We have a configuration option in website_configurations but there's not automatic detection (meaning you have to go there and change it). Also, turning it off is untested for now.
What about logger.error "blah blah blah"?
2 options here: 1. Simply add another OR clause to the question search SQL in question.rb around line 473 to implement search by author 2. Add another drop down menu...
Note: Whether or not we keep can_read in the controller, it also needs to be translated to SQL in order for pagination to be efficient.
You could do that. Make sure you don't miss anything though (models, views, controllers, tests, helpers, test helpers)
Yes you should :) But really you just need to test the instances where message behavior differs from general comment behavior (after all they are related).