Jeremy Daer 565094a8b5 Use Mime[:foo] instead of Mime::Type[:FOO] for back compat ... Rails 4.x and earlier didn't support `Mime::Type[:FOO]`, so libraries that support multiple Rails versions would've had to feature-detect whether to use `Mime::Type[:FOO]` or `Mime::FOO`. `Mime[:foo]` has been around for ages to look up registered MIME types by symbol / extension, though, so libraries and plugins can safely switch to that without breaking backward- or forward-compatibility. Note: `Mime::ALL` isn't a real MIME type and isn't registered for lookup by type or extension, so it's not available as `Mime[:all]`. We use it internally as a wildcard for `respond_to` negotiation. If you use this internal constant, continue to reference it with `Mime::ALL`. Ref. efc6dd550e		2015-10-06 11:29:30 -07:00
..
abstract	Use Mime[:foo] instead of Mime::Type[:FOO] for back compat	2015-10-06 11:29:30 -07:00
assertions	use a lookup table for assert_response	2015-07-13 18:10:36 -07:00
controller	Use Mime[:foo] instead of Mime::Type[:FOO] for back compat	2015-10-06 11:29:30 -07:00
dispatch	Use Mime[:foo] instead of Mime::Type[:FOO] for back compat	2015-10-06 11:29:30 -07:00
fixtures	Add failing spec on utf8 filename with percent character	2015-08-04 21:27:22 +09:00
journey	Remove TestRouter#add_routes	2015-09-29 13:43:11 +09:00
lib/controller	Removing unused fake models	2014-09-07 22:51:14 -03:00
routing	Remove deprecate *_path helpers in email views	2015-01-04 11:58:42 -03:00
tmp
abstract_unit.rb	mostly remove the ParamsParser middleware	2015-09-18 15:36:55 -07:00