rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	active_support/dependencies/autoload is already required via active_support.rb	Akira Matsuda	2019-07-12	1	-3/+0
\|
*	Rails 6 requires Ruby 2.4.1+	Jeremy Daer	2018-02-17	1	-6/+0
\| \| \| \| \| \|	Skipping over 2.4.0 to sidestep the `"symbol_from_string".to_sym.dup` bug. References #32028
*	[Active Support] require_relative => require	Akira Matsuda	2017-10-21	1	-7/+7
\| \| \| \|	This basically reverts 8da30ad6be34339124ba4cb4e36aea260dda12bc
*	[Active Support] `rubocop -a --only Layout/EmptyLineAfterMagicComment`	Koichi ITO	2017-07-11	1	-0/+1
\|
*	Use frozen-string-literal in ActiveSupport	Kir Shatrov	2017-07-09	1	-0/+1
\|
*	[Active Support] require => require_relative	Akira Matsuda	2017-07-01	1	-7/+7
\|
*	let Regexp#match? be globally available	Xavier Noria	2016-10-27	1	-0/+6
\| \| \| \| \| \|	Regexp#match? should be considered to be part of the Ruby core library. We are emulating it for < 2.4, but not having to require the extension is part of the illusion of the emulation.
*	applies new string literal convention in activesupport/lib	Xavier Noria	2016-08-06	1	-6/+6
\| \| \| \| \|	The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
*	[ci skip] Update ActiveSupport::Rails and ActiveSupport::Rescuable docs	DAVID MOORE	2015-04-26	1	-2/+2
\| \| \| \|	[Dave Moore]
*	removes usage of Object#in? from the code base (the method remains defined ↵	Xavier Noria	2012-08-06	1	-3/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	by Active Support) Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple \|\| is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case.
*	load active_support/deprecation in active_support/rails	Xavier Noria	2012-08-02	1	-0/+3
\|
*	load active_support/core_ext/module/delegation in active_support/rails	Xavier Noria	2012-08-02	1	-0/+3
\|
*	load active_support/core_ext/class/attribute in active_support/rails	Xavier Noria	2012-08-02	1	-3/+6
\|
*	load active_support/concern in active_support/rails	Xavier Noria	2012-08-02	1	-0/+3
\|
*	load active_support/dependencies/autoload in active_support/rails	Xavier Noria	2012-08-02	1	-0/+3
\|
*	load active_support/core_ext/object/inclusion in active_support/rails	Xavier Noria	2012-08-02	1	-0/+4
\|
*	load active_support/core_ext/object/blank in active_support/rails	Xavier Noria	2012-08-02	1	-0/+2
\|
*	defines a private require-hub active_support/rails	Xavier Noria	2012-08-02	1	-0/+9
	This is a private place to put those AS features that are used by every component. Nowadays we cherry-pick individual files wherever they are used, but that it is not worth the effort for stuff that is going to be loaded for sure sooner or later, like blank?, autoload, concern, etc.