rails--rails/activerecord/test/models/mixed_case_monkey.rb

# frozen_string_literal: true

class MixedCaseMonkey < ActiveRecord::Base
  belongs_to :human
end
Use frozen-string-literal in ActiveRecord 2017-07-09 13:41:28 -04:00			`# frozen_string_literal: true`

Consistently quote primary key column names. Closes #7763. git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6364 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2007-03-08 22:23:37 -05:00			`class MixedCaseMonkey < ActiveRecord::Base`
Replace test `Man` with `Human` The commit replaces the `Man` model used in tests with a `Human` model. It also replaces the existing `Human` model with a `SuperHuman` model inheriting from `Human`. While this may seem like a cosmetic change, I see it as more of an inclusivity change. I think it makes sense for a number of reasons: * Prior to this commit the `Human` model inherited from `Man`. At best this makes no sense (it should be the other way around). At worst it is offensive and harmful to the community. * It doesn't seem inclusive to me to have exclusively male-gendered examples in the codebase. * There is no particular reason for these examples to be gendered. * `man` is hard to grep for, since it also matches `many, manager, manual, etc` For the most part this is a simple search and replace. The one exception to that is that I had to add the table name to the model so we could use "humans" instead of "humen". 2020-08-13 18:11:28 -04:00			`belongs_to :human`
Consistently quote primary key column names. Closes #7763. git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6364 5ecf4fe2-1ee6-0310-87b1-e25e094e27de 2007-03-08 22:23:37 -05:00			`end`