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
..
abstract	Move abstract's controller tests to AV	2013-08-25 11:40:11 +02:00
assertions	test response assertions	2012-01-06 11:20:26 -08:00
controller	Eliminate JSON.{parse,load,generate,dump} and def to_json	2013-11-05 22:26:45 -08:00
dispatch	Revert "Merge pull request #9660 from sebasoga/change_strong_parameters_require_behaviour"	2013-11-02 14:30:03 -05:00
fixtures	Fixing repond_with working directly on the options hash	2013-10-09 12:36:26 +03:00
journey	Eliminate JSON.{parse,load,generate,dump} and def to_json	2013-11-05 22:26:45 -08:00
lib/controller	Eliminate JSON.{parse,load,generate,dump} and def to_json	2013-11-05 22:26:45 -08:00
routing	Fix failing test missed for the past year :(	2013-07-17 08:56:34 +01:00
tmp
abstract_unit.rb	Remove RenderERBUtils from AP (only AV use it)	2013-08-25 11:39:10 +02:00