alassek / jquery.rest Goto Github PK

First, congratulations for writing a very useful plugin. I'm trying to use it in combination with inherited_resources, and although the "read" action works, "update" only returns an empty hash, even though I get a "success" 200 status code.

How should I configure my controller to get it to work? Right now all I have is this:

class Admin::DesignersController < Admin::BaseController

  respond_to :html, :json

end

(with BaseController inheriting from inherited_resources)

Currently sending data as text/html. We should automatically set the content-type header when:

• User defines $.restSetup.contentType
• Url includes a resource ending in .json or .xml

Perhaps I should provide an API for setting headers.

According to this article didn't you misunderstood difference between PUT and POST ? Just ask ;)

IE < 9 don't support PUT or DELETE so we still need to tunnel requests for those browsers.

Double-check browser support for PUT and DELETE in standards-compliant browsers.

Some JSON APIs require sending application/json to the server instead of application/x-www-form-urlencoded.

Rework data-object and url-substitution code to support using JSON.stringify instead of jQuery.param.

Related to #12

The rails 3 ujs driver defines a beforeSend function which is expecting a settings object so it can set correct accept headers. I'm seeing two problems with jquery.rest. First, on line 139 the apply method is being called on userBeforeSend, but apply requires an array as its second argument. I believe this should be:

if ( $.isFunction(userBeforeSend) ) userBeforeSend.call(context, xhr);

But even though that works, because the ujs driver is expecting a settings object you get a typeerror when that line runs. I'm not familiar enough with js or jquery to fix it myself. If you could point me in the right direction, I'd be happy to submit a pull request.

Hi,

i like principle of REST queries for jQuery, that is really great idea. But i don't know where is problem.

I write simple ordering with acts_as_list, jQuery sortable and jQuery.REST.

Have this action in categories controller:

  def update_position
    params[:category].each.with_index do |id, index|
      Category.update_all({position: index+1}, {id: id})
    end

    index
  end

After update i want to update positions in HTML table. so have this view:
update_position.js.erb

<%- @categories.each do |category| %>
  $('#' + '<%= dom_id(category) %>' + ' .position').html(<%= category.position %>);
<%- end %>

But when is JS event called with

$.update(
  $(this).data('update-url') + '.js', $(this).sortable('serialize')
);

it is returned like JSON (Accept header is application/json at first, second is text/javascript what i want), so my view isn't executed. But when i call event with normal post query:

$.post(
  $(this).data('update-url') + '.js', $(this).sortable('serialize');
);

it is executed.

Hi,

I find that GET requests are caching for me in IE7 when I try a $read against a resource. As a workaround I have changed the read() function in the jquery.rest code to be:

 function read () {
   collect_options.apply(this, arguments);
   $.extend(options, { type: 'GET' })
   $.extend(options, { cache: false }) // STOP IE CACHING
   return $.ajax(options);
 }

However, is there a way I can pass this { cache: false } into the $read() method from my calling code - instead of modifying the code in into jquery.rest framework? I see you mention the following in the README:

"In addition to these parameters, you can simply pass a standard jQuery.Ajax options object instead as the only parameter"

However, I want to just supress caching.

Thanks again for publishing jquery.rest. I find it quite useful.

Regards,
Declan