params

In extjs3.x I used the stores baseParams config property to specify parameters used to load the store. This property no longer exists in extjs 4. What should I do instead of this? Also in extjs3 I was able to specify wether the stores proxy was a GET or a POST method by using the proxy method config property. What should I do instead of this? My ExtJs 3 code -> var store = new Ext.data.JsonStore({ root: 'Data', baseParams: { StartDate: '', EndDate: ''' },//baseParams proxy: new Ext.data.HttpProxy({ url: 'Time/Timesheet', method: 'POST' })//proxy });//new Ext.data.JsonStore You need to use the

I've got an iPhone app requesting an API, and it uses a nested param structure to pass in a username and password to login. In my Rails controller, I'm successfully retrieving this information normally using: username = param[:session][:username] I'd like to test my API from shell, using cURL. But I can't figure out how to provide nested params? The code below does NOT work... And I've tried multiple variations. But just can't seem to figure it out? curl -d '{"session":{"username":"test","password":"password"}}' http://testurl/remote/v1/sessions Any help, much appreciated! Different frameworks

I'm trying to get some more information into my Rails logs, specifically the requested URI or current params, if available (and I appreciate that they won't always be). However I just don't seem able to. Here's what I've done so far: #config/environments/production.rb config.logger = Logger.new(config.log_path) config.log_level = :error config.logger.level = Logger::ERROR #config/environment.rb class Logger def format_message(level, time, progname, msg) "**********************************************************************\n#{level} #{time.to_s(:db)} -- #{msg}\n" end end So I can customize

Why cant I use an IEnumerable with params? Will this ever be fixed? I really wish they would rewrite the old libraries to use generics... Why cant I use an IEnumerable with params? The question presupposes that the design team must provide a reason to not add a feature to the language. This presupposition is false. Rather, in order for a feature to be used by you it needs to be thought of, designed, specified, implemented, tested, documented and shipped. All of these have large costs. The "params enumerable" feature has been thought of and designed. It has never been specified, implemented,

When a User submits via private how can we hide the submitted info from the feed and from other users being able to see it on his public profile? <%= button_tag(type: 'submit', class: "btn") do %> ... <%= button_tag(type: 'submit', class: "btn", id: "2", name: 'private') do %> ... We put the below in the controller, but since the private button will be in a lot of different _forms, do I have to put it in each controller or can we put it in the application controller? if params[:private] # the private action / What do we need to put here? else # normal submit / and here? I followed this

I have the following method: void MyMethod(params object[] args) { } which I am trying to call with a parameter of type object[] : object[] myArgs = GetArgs(); MyMethod(myArgs); It compiles fine, but inside MyMethod I args == { myArgs} , i.e. an array with one element that is my original arguments. Obviously I wanted to have args = myArgs , what am I doing wrong? EDIT: Jon Skeet was actually right, the GetArgs() did wrap the thing in an one element array, sorry for stupid question. What you've described simply doesn't happen. The compiler does not create a wrapper array unless it needs to.

In Rails 3 (Ruby 1.9.2) I send an request Started GET "/controller/action?path=/41_+" But the parameter list looks like this: {"path"=>"/41_ ", "controller"=>"controller", "action"=>"action"} Whats going wrong here? The - , * or . sign works fine, its just the + which will be replaced by a space. That's normal URL encoding, the plus sign is a shorthand for a space : Within the query string, the plus sign is reserved as shorthand notation for a space. Therefore, real plus signs must be encoded. This method was used to make query URIs easier to pass in systems which did not allow spaces. And