On 15/12/2006, at 11:40 AM, Dan Manges wrote: > At a minimum, Rails could issue a warning that "plugin xyz may not be > compatible with the version of Rails you're using." It may not be > critical at this stage, but a few more 1.x releases, and definitely > after deprecated code is _removed_ in 2.0, I think it would be > valuable.
I say let people add this to the plugin if you know your plugin is messing with internals. A lot of plugins don't mess with internals and are A OK for 1.0+ apps. A standard method to check the version of Rails on plugin init and produce a (silence-able) warning (like the deprecation warnings) might be handy though. It'll at least encourage hacky plugins to be up front about forward-compatibility. -- tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
