Forgot to mention I'd also like to try and find a creative way to not have to forcefully require the JSON gem (activesupport/lib/ active_support/json/encoding.rb:13) even if the coder never intends on using it.
-Brian On Jan 20, 9:34 am, brianmario <seniorlo...@gmail.com> wrote: > I'd also like to wrap up a patch re-enabling streaming params parsing. > I have it started (http://gist.github.com/281693) and am in the > process of figuring out how to write the tests - given we need to > ensure the backends work when parsing from a Rack-compatible IO > object. Josh set me off in the right direction so I expect to be done > soon. > > Also, I've had a ticket open for a while to officially get the yajl- > ruby backend in Rails core as one of the supported JSON decoding > backends. I can supply a patch for that soon as well. Fwiw, my fork of > technoweenie's yajl-rails plugin (enabling it as a backend) is up to > date as of rails 2.3.5 and from what I can tell in the code in Rails 3 > it may be compatible with it as well.http://github.com/brianmario/yajl-rails. > The link to the yajl-ruby ticket > is:https://rails.lighthouseapp.com/projects/8994/tickets/2666-yajl-ruby-... > > -Brian > > On Jan 20, 4:54 am, thelucid <ja...@soniciq.com> wrote: > > > > > Hi Yehuda, > > > Great news. > > > There are a number of areas in ActiveModel where assumptions are made > > that your attributes exist via methods, I have briefly discussed this > > with José Valim. There needs to be another hook method like > > read_attribute_for_validation for the dirty module and a few other > > places. I am happy to go ahead with this if required, I believe the > > before_type_cast stuff assumes methods too. > > > Kind regards, > > > Jamie > > > On Jan 20, 9:59 am, Yehuda Katz <wyc...@gmail.com> wrote: > > > > Hey everyone, > > > > We're closing in on the release of the Rails 3 beta. At the moment, we're > > > focusing on finalizing a number of APIs, including the new Railtie API, > > > generators, the bundler, the new notification system, and a few more > > > things. > > > In all of these cases, the core code has been written, and we're seeing > > > how > > > it feels to use the APIs in real plugins and applications, tweaking as we > > > go. > > > > In short, we're pretty close to releasing a beta. We'd like the beta to be > > > our best-attempt at feature/API complete, with the explicit > > > acknowledgement > > > that once a lot more people start working with the code, gaps and errors > > > will need to be corrected. > > > > If you're aware of any gaps or errors that exist today in areas like > > > ActionController, ActiveModel, or ActiveRecord, please let us know so we > > > can > > > make sure to get them corrected before the release. Feel free to take a > > > look > > > at the work going into Railties as well, but be aware that it's still > > > undergoing rapid API refinement, and most obvious gaps are on the short > > > list > > > to resolve before the beta. > > > > So... if you have any patches for master, now's the time! > > > > Yehuda Katz > > > Developer | Engine Yard > > > (ph) 718.877.1325
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
