search for: rafaelmfranca

...but it doesn''t. It > • wouldn''t take much to modify the filter method linked above to evaluate > • all procs passed in as options. I''m going to make a pull request unless > • there are any objections. > •   > • "Rafael Mendonça França" <rafaelmfranca@gmail.com> Dec 13 06:28PM -0300   > • > • Action cache was extracted from Rails and it is not part of the framework > • anymore. > •   > • Rafael Mendonça França > • http://twitter.com/rafaelfranca > • https://github.com/rafaelfranca > •   > •   > •   &gt...

Last night a friend of mine started ranting about validates_presence_of :boolean_field returning not valid when the boolean field is false. I checked the rails issues and this seems to be a pretty common concern about the naming of ''presence'' . Instead of changing the behaviour of the presence validator, I was wondering if maybe the answer to avoid such misconceptions could be

I''m probably going to help backport some code from master onto 3.2, and the suggested process in the Contributing guide doesn''t actually look like the best approach to me. Wouldn''t it make more sense to just check out the branch you want to patch, cherry-pick the change(s) from master, make any additional commits necessary to get it working? Not only is that simpler

(I posted this as a bug in GitHub (https://github.com/rails/rails/issues/7018), but then someone there told me I should post it here, so here it is.) If you set attr_accessible on some properties in an ActiveRecord-descended class, and then attr_protected on others - the class becomes ''default-open'' - if any properties are missed or added later, they will be accessible by

There''s a small inconsistency in ActiveRecord''s callback syntax that has tripped me up before. It wouldn''t be a big deal, but it can lead to a silent failure. I''d like to suggest that it either be made consistent or be made to fail loudly. The issue is that to do something before validating, but only when creating, you use `before_validation on: :create`,

We found two regressions. One on Active Record and one on Action Pack. Took some time to fix those issues so the release was delayed until today. Here are the changes from 4.0.1.rc3 to 4.0.1.rc4: https://github.com/rails/rails/compare/v4.0.1.rc3...v4.0.1.rc4 And the changes from 4.0.0 to 4.0.1: https://github.com/rails/rails/compare/v4.0.0...v4.0.1.rc4 If we don''t hit any more

Hi everyone, I am happy to announce that Rails 4.0.4.rc1 has been released. This is a bug fix release and includes more than 290 commits. If no regressions are found we will release 4.0.4 final this Friday, on March 14, 2014. If you find one, please open an Issue on GitHub and mention me (@rafaelfranca) on it, so that we can fix it before the final release. ## CHANGES since 4.0.3 To view the

Hi everyone, I am happy to announce that Rails 4.0.1.rc1 has been released. This is a bug fix release and includes more than 450 commits. This release comes up with an important change on how Active Record handles subsequent `order` calls. In Rails 4.0.0 when you do something like this: ```ruby User.order("name asc").order("created_at desc") ``` The later called `order`