> Koz and I discussed this on IRC. I think his plan was to send an
> email to this list indicating plans to deprecate the postgres gem in a
> future version. You just beat him to it :)
Indeed, this was basically the email I intended to send :)
> The current state is that
> geminstaller.yml onl
> So Rails should never really generate any JS for these helpers. Just
> decorate them with the proper class names/attributes.
Ok, I'll start working on this in the next few days and keep you
updated on the progress.
> Obviously, I like that too - otherwise I wouldn't have made the
> suggestion
On Thu, Jan 29, 2009 at 5:09 AM, Mike Gunderloy wrote:
> One possible resolution would be for us to have both gems available on
> the CI server, and to increase the sophistication of the build script
> to run the AR tests using each one in isolation - I know Chad Woolley
> was looking into this.
I'm using Ruby 1.9.1-rc2 (ruby 1.9.1p0 (2009-01-20 revision 21700)
[i386-darwin9.5.0]) and trying to run unit tests for AS.
I noticed an endless loop for all the cases which are using XmlMini,
which is autoloaded:
autoload :XmlMini, 'active_support/xml_mini'
Autoload expect to find ActiveSupport
I'm not convinced that
http://github.com/rails/rails/commit/feed7b4cfd860bdc9f5b4efc2ca2af76cb01d55d
(simply replacing the postgres gem with the pg gem in the CI server
setup instructions) is the right resolution. We had a mystery build
break yesterday which pointed to the PostgreSQL AR te
See the discussion on the ticket for a nice lazy evaluation feature
using blocks.
-Tim
On 29 Jan., 13:03, "matthewrudyjac...@gmail.com"
wrote:
> On Jan 29, 11:56 am, stephen paul suarez wrote:
>
> > how do you suggest to make it cater for fallbacks that doesn't necessarily
> > belong to a meth
On Jan 29, 11:56 am, stephen paul suarez wrote:
> how do you suggest to make it cater for fallbacks that doesn't necessarily
> belong to a method
> in the object?
> e.g.:
>
> user.name.blank? ? user.name : "An arbitrary value"
>
> --stephen
BumbleBees are very versatile creatures.
And they retu
how do you suggest to make it cater for fallbacks that doesn't necessarily
belong to a method
in the object?
e.g.:
user.name.blank? ? user.name : "An arbitrary value"
--stephen
On Thu, Jan 29, 2009 at 7:47 PM, matthewrudyjac...@gmail.com <
matthewrudyjac...@gmail.com> wrote:
>
>
> On Jan 29, 1
On Jan 29, 10:59 am, "matthewrudyjac...@gmail.com"
wrote:
> >> user.bumblebee
> (:full_name, :email, :something_else, :another_fallback)
I cemented the BumbleBee in a gist.
http://gist.github.com/54501
--~--~-~--~~~---~--~~
You received this message because
On Jan 28, 6:25 am, Ryan Angilly wrote:
>
> I also realized that I do crap like this a lot too:
>
> self.owner_object_association ? self.owner_object_association :
> default_thing
>
> Where this would give me:
>
> self.owner_object_association.or_if_blank? default_thing
I really don't like "or_
Obviously, I like that too - otherwise I wouldn't have made the
suggestion half a year ago! :-) Make sure that you contact me as soon
as something's decided - I'd be happy to help implementing this!
- Clemens
On Jan 29, 3:36 am, Mislav Marohnić wrote:
> On Thu, Jan 29, 2009 at 00:25, DHH wrote
11 matches
Mail list logo
