Godfrey Chan ff1192fea4 Eliminate JSON.{parse,load,generate,dump} and def to_json ... JSON.{dump,generate} offered by the JSON gem is not compatiable with Rails at the moment and can cause a lot of subtle bugs when passed certain data structures. This changed all direct usage of the JSON gem in internal Rails code to always go through AS::JSON.{decode,encode}. We also shouldn't be implementing `to_json` most of the time, and these occurances are replaced with an equivilent `as_json` implementation to avoid problems down the road. See [1] for all the juicy details. [1]: intridea/multi_json#138 (comment)		2013-11-05 22:26:45 -08:00
..
http	✂️ [ci skip]	2013-11-04 13:01:57 -02:00
journey	Eliminate JSON.{parse,load,generate,dump} and def to_json	2013-11-05 22:26:45 -08:00
middleware	Revert "Merge pull request #9660 from sebasoga/change_strong_parameters_require_behaviour"	2013-11-02 14:30:03 -05:00
request	add the fetch method to sessions	2013-10-29 20:37:15 +01:00
routing	Respect SCRIPT_NAME when using redirect with a relative path	2013-10-10 13:03:26 +01:00
testing	Fix incorrect assert_redirected_to failure message	2013-09-19 09:23:20 -04:00
journey.rb
railtie.rb	Don't set X-UA-Compatible header by default	2013-06-13 14:56:02 -05:00
routing.rb	Dry-up ActionDispatch::Routing autoloads	2013-06-04 12:12:52 +03:00