Akira Matsuda 530f7805ed It may be better to explicitly require 'object/try' where we call try ... In most cases it works now without explicit require because it's accidentally required through active_support/core_ext/date_and_time/calculations.rb where we still call `try`, but that would stop working if we changed the Calculations implementation and remove the require call there.		2019-08-01 18:51:51 +09:00
..
analyzer	Revert "Merge pull request #36676 from wjessop/change_activestorage_metadata_duration_to_bound"	2019-07-17 09:59:03 +09:00
controllers	Remove outdated cross-origin redirection tests	2019-05-15 15:57:45 -04:00
database	Refactor migration to move migrations paths to connection	2018-01-18 08:55:03 -05:00
dummy	Let the generated initializers/backtrace_silencers.rb code use Regexp#match?	2019-07-29 14:21:30 +09:00
fixtures/files	Use a smaller TIFF file as fixture	2019-07-27 23:08:49 +05:30
jobs	Remove superfluous test	2018-08-19 01:10:50 -04:00
models	Preserve existing attachment assignment behavior for upgraded apps	2019-07-20 06:33:11 -04:00
previewer	Change video preview format from PNG to JPG	2018-05-23 14:32:34 -04:00
service	Merge pull request #36792 from peterzhu2118/azure-content-disposition	2019-07-31 18:44:58 -04:00
template	url -> URL where apt except inside actionpack/	2019-04-01 22:56:35 +05:30
test_helper.rb	It may be better to explicitly require 'object/try' where we call try	2019-08-01 18:51:51 +09:00