Re: #to_json incompatibilities between ActiveSupport & JSON gems

Kenneth Kalmer
2008-12-02T06:50:58Z

On Mon, Dec 1, 2008 at 6:54 PM, Michael Koziarski <michael@koziarski.com>
wrote:
>
>> Agreed. For my example above it works perfectly well, since
I''m not really
>> concerned with the Time instances. They''re just part of a JSON
payload, and
>> I control only part of the payload (where time doesn''t
matter).
>
> OK, so from my perspective the ideal solution would be that you can
> just tell your users to require the json gem *after* activesupport,
> and have everything ''just work'' because it nukes our
methods.  If
> that''s not the case, lets fix it.

Obvious, but how many others are aware of this. Maybe have
ActiveSupport emit a warning message when it detects the presence of
the JSON gem, telling users who rely on the JSON gem to include it
afterwards? This doesn''t fiddle with anything, and gives the user
great feedback.

Best