David Chelimsky

FWIW, I think that having to know that the .where and conditions work differently is confusing and puts an unnecessary burden on users, even if everything is vi...

José and I discussed this a bit and agree that this does not add value that can't be achieved in other ways. Please feel free to close.

FYI - the updated patch is rebased off a more recent master. Everything is passing now for me.

Updated patch: https://github.com/dchelimsky/rails/commit/787407c40db54d6ea87308e2...

That seems fine to me, as long as persisted? returns false if it's been destroyed. Do you want me to make that change in my patch? Or merge what I've got and up...

Note that new_record? is not removed by this change (that would not be so good for the myriad extensions rely on it). The change is that ActiveRecord uses persi...

ActiveModel introduced the persisted? method (inverse of new_record?), but ActiveRecord still uses new_record? internally and across associations. This means th...

@DavidTrasbo, please have at it. Thanks!

Consider:

class WelcomeController < ApplicationController
  def index
    cookies[:foo] = "bar"
    cookies["baz"] = "bam"
  end
end


class WelcomeControllerT...

Spoke w/ José and we agreed view_assigns should be added and _assigns deprecated on the 3-0-stable branch (so _assigns can be removed from 3.1).

Here's a new pa...