Displaying 4 results from an estimated 4 matches for "query_param".
Did you mean:
query_params
2008 May 08
2
Testing render :text without has_text
...pare that with the expected objects. To do this, I need RSpec to
give me the complete text string that''s rendered by the controller.
Here''s the controller:
class StatsController < ApplicationController
layout nil
def query
reports = StatisticsReporter.query params[:query_params]
render :text => Marshal.dump(reports)
end
end
And here''s the test:
describe StatsController do
before :each do
@query_params = { :foo => :bar }
end
it "should return a demarshallable string of the reports" do
reports = [
StatisticsReport....
2008 Apr 23
0
self referential (n-n relationship) belongs many controller
...;'], ''id'', ''ASC'')
search = {:id => @params[:id], :statut_id => @params[:statut_id],
:description => @params[:description], :acteur => @params[:acteur]}
if search[:id] && search[:id] != ''''
query ||= []
query_params ||= []
query << "id = ?"
query_params += [search[:id]]
end
if search[:statut_id] && search[:statut_id] != ''''
query ||= []
query_params ||= []
query << "statut_id = ?"
query_params += [search[:stat...
2009 Mar 15
0
rspec-rails 1.2.0 Released
...layout and stylesheet (per Rails-2.3)
* add bypass_rescue for controller specs
* infer template path from the first arg passed to describe in view specs
* separate routing specs (in spec/routing)
* bug fixes
* you no longer *have* to load ActionMailer to get specs to run. Closes #650.
* query_params are now parsed by Rack::Utils.parse_query in
redirect_to matcher. Closes #684.
* cleaned up spec_server (there was a bunch of pre-rails 2.0
material). Closes #685.
* rspec''s rake tasks are not loaded when running "rake gems" or any
of its subtasks
* only warn when rspec is...
2007 Sep 18
10
Routes
hi all,
I want to move some routing tasks out of the router and into the
controller. The goal is to make Merb feel less like mod_rewrite and
give the user more control at the controller. The new Router is
simple: it takes the path_info (not the whole request) then outputs a
controller class and some parameters from the path matching. The rest
of the routing would be done at the controller level.