similar to: Patch for serious nil response bug when Action caching responses that are not cacheable

I''d really like to see just 2 more functional changes to the JSON serialization/encoding before we get to Rails 2.0. First, and I think this is really crucial because without it all the efforts to output JSON from ActiveRecord objects would have been half in vain, is to allow us to do this in controllers: @authors = Author.find(:all) render :json => @authors.to_json(:only =>

Hi devs, I was trying to open a new ticket with a minor doc patch at the BackgroundDrb Trac (http://backgroundrb.devjavu.com/) and it seems like only admins have permission to do so. Is this intended? I read in the readme that patches should be mailed to this list, but I much prefer to use Trac since there''s already one set up. Any reason Trac is not open to registered Devjavu users?

Just a quick pointer to some ActiveSupport patches hoping for reviews: Puts Array#to_query and Object#to_query in the right places in ActiveSupport - http://dev.rubyonrails.org/ticket/10395 Preserve user-specified content type for XML and JSON rendering (currently it''s overridden and set to Mime::XML/Mimi::JSON - http://dev.rubyonrails.org/ticket/10388 Oh and a tiny patch for

Please check out this ticket (which would explain almost everything): http://dev.rubyonrails.org/ticket/8762 So basically, Rails to_json methods produces invalid JSON out of the box as it doesn''t quote all hash keys. This is valid JSON: { "id": 6589, "code": "SIN", "name": "Singapore" } This is not (Rails'' JSON encoders

I like the merb-style exception pages where there''re links to open the files listed in the stack trace in TextMate and the source around each line a lot so I stole the idea (and the code!) and made a patch for Rails: http://dev.rubyonrails.org/ticket/10401 Here''s how it looks like in Merb: http://yehudakatz.com/wp-content/uploads/stacktrace.gif What do you guys think?

Sorry for attaching patches in emails to the mailing list, but I''m still unable to login to Devjavu for Backgroundrb (I''m able to login just fine for Merb''s Devjavu and submitted a ticket successfully). Anyway, I encountered a bug when trying to #ask_status of a worker before it''s run (or rather, before its result_hash has been set to something). Not sure why

Hi all, I just submitted a patch that would allow you to pass a proc to ActionController::Base.asset_host rather than just using a %d wildcard (e.g. assets%d.example.com). Basically this frees you from the hard-coded assumption that you have 4 hosts numbered 0-3 and also allows you to do smarter things depending on the asset (e.g. images from a particular domain, stylesheets from another). The

Hi guys, Could a core committer review and apply http://dev.rubyonrails.org/ticket/10602? This would get rid of a failing test with the latest version of mocha (0.5.6). Thanks much! Cheers, Chu Yeow --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send

I''m really glad the JSON changes got in, many thanks to all involved, committers and contributors alike :). But there''s still one feature that''s missing to achieve feature parity between the JSON and XML encoding/conversion. And that is the abililty to say in your controller: @authors = Author.find(:all) render :json => @authors.to_json(:only => :name)

Just some quick cleanup and documentation. Remove obsolete ActiveSupport::JSON::Variable - http://dev.rubyonrails.org/ticket/9969 Add documentation for Hash#to_json and Enumerable#to_json - http://dev.rubyonrails.org/ticket/9970 Please review :) Thanks! Cheers, Chu Yeow --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google

In case Rails 2.0 gets released without these bits of documentation regarding the recent JSON changes, I''d like to highlight some docfixes: http://dev.rubyonrails.org/ticket/9833 and http://dev.rubyonrails.org/ticket/9814 Could a committer could take a quick look? Thanks! Cheers, Chu Yeow --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

Hi again everyone, I''ve 2 tiny doc patches mostly involving grammar fixes (and errant whitespace elimination). My English is not perfect so any review would be very welcome. The patches: http://dev.rubyonrails.org/ticket/9819 http://dev.rubyonrails.org/ticket/10062 Thanks! Cheers, Chu Yeow --~--~---------~--~----~------------~-------~--~----~ You received this message because you

Hi all, I wanted to draw some attention to a couple of very small multibyte-related patches I believe should be included before Rails 3.0 RC1: * Use String#bytesize rather than String#length in exception templates: This is a simple case where string length is checked, but bytes is needed, so it breaks with string with multibyte chars.

Hi, when trying to migrate Signal to Rails 3 I tried to use the shorthand route for: match ''/projects/status(.:format)'' but it thrown an error because the controller was not specified. This happend because actually the shorthand routes only work with routes without optional parameters. The modification to support routes ending with a optional parameters is very simple, as can

I''ve submitted a couple of patches in Ligththouse. Provide NoStore implementation of ActiveSupport::Cache::Store This patch provides a NoStore implementation of ActiveSupport::Cache::Store suitable for use in development and test environments where the code need to use the cache interface, but actually caching data is not desired.

The way Rails handles root nodes in JSON and XML serialization is inconsistent. This has been discussed before: https://rails.lighthouseapp.com/projects/8994/tickets/2584-232-activeresource-json-doesnt-send-parameters-with-root-node This seems mostly taken care of with ActiveModel::Base.include_root_in_json, especially if/when it ends up in ActiveResource. However, there is also the issue of how

Fix for the bad (failing) test here: http://dev.rubyonrails.org/ticket/10664 On Jan 2, 5:33 pm, alexey.verkhov...@gmail.com wrote: > The build failed. > > CHANGES > ------- > Revision 8522 committed by bitsweat on 2008-01-02 09:03:56 > db:sessions:clear task uses session_table_name method. Closes #10631 [Cheah Chu Yeow] > > M /trunk/railties/lib/tasks/databases.rake >

Hi, I'm having a problem getting my Windows machines to access shares in Samba. When they browse to the Samba box it sometimes gives them an error saying that they don't have permission or that the server is unavailable. However this doesn't always happen and other times it lists the shares. When I try to access the shares it just prompts for the username/password over and over.

Hi, I noticed that 2 days ago that this ticket was marked "stale". https://rails.lighthouseapp.com/projects/8994/tickets/6171 But the issue is still here (I checked just now), and it reminded me I had a patch for it I forgot to submit, so I attached the patch file to the ticket. Since I''m still new on this, can someone please point me the right procedure ? Should I have

Hello! Could someone review the patch attached to [1] and provide feedback? Briefly, it targets rails 3, and fixes "rails g model admin/post". The generated migration creates a "admin_posts" table while the model expects a table simply named "posts". With the patch, the migration creates "posts". Thank you! --phil-- [1]