On Mon, Dec 1, 2008 at 6:54 PM, Michael Koziarski <[EMAIL PROTECTED]> 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 -- Kenneth Kalmer [EMAIL PROTECTED] http://opensourcery.co.za --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
