This project is archived and is in readonly mode.
config.load_paths gone, but no deprecation warning.
-
José Valim
- Importance changed from to Low
Please provide a patch that adds the required deprecations here:
http://github.com/rails/rails/blob/master/railties/lib/rails/config...
Thanks!
-
Xavier Noria
Please if you do this patch say it will be removed in final. Rails 3 is gonna use autoload_paths.
This is a change in a beta, RC will be frozen in this sense and won't have changes like this (unless something critical shows up, you know). So it is a warning just between beta and final.
-
James Harton
You don't think that the deprecation warning should be present in every release up to the point where it is removed?
-
Xavier Noria
Yes, but there's no release of Rails 3 yet.
The golden path for an application in Rails 2 is to first upgrade to the last 2.3, that is, the one released together with Rails 3. There you get rid of all warnings, and then you start with Rails 3 proper.
In my view it is OK to break prereleases like that within some common sense, you know there's a lot going on occasionally some incompatibility is introduced for the benefit of final.
That's why I didn't introduce a warning in master, if you are upgrading betas I prefer that the application clearly manifests you need to change that. Otherwise you may not notice until final, which is gonna be worse.
-
José Valim
Could someone please provide a patch or this can be closed?
-
José Valim
- State changed from new to invalid
Ok, I'm closing this. If anyone feels like contributing a patch, I will reopen.