On 2006-07-26, at 16:16 , Kevin Clark wrote:
The things that are planned sound great. Expanding on Ryan's idea, I think using deprecated methods should be considered an error. Once the code goes in, I'd like to write a plugin that raises a deprecation exception (when in the test environment) if deprecated methods are used. I trust it's just a matter of plugging into some hook?
That would depend on how they decide to implement it. If they use the same method to warn about all deprecations, changing it to raise would be as simple as overriding that method.
One could also change it to email the coder on each deprecated call. The possibilities are endless :P
I also like the idea of the code scanner task, even if it's unreliable. It may detect things that are otherwise undetecable, such as the use of @content_for_layout
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
