3 ms·
The replacement is almost always available at the time of deprecation. Old things get deprecated precisely because there is a replacement.
by twic 3y ago
The replacement is almost always available at the time of deprecation. Old things get deprecated precisely because there is a replacement.
- alias_neo 3y agoOf course. I think you and the other commenter missed my point. If you go from version 4 (say), to version 7 (say,several years later), something could have been deprecated in 4/5 and removed entirely in 6/7, you've missed the transition period between the thing being deprecated and it being removed entirely. There's no way you're going to use the method in OP to "fix" all of the problems you'll encounter going from 4 all the way to 7 without just going to 7 and fixing everything that's broken.
- murkt 3y agoThere sure is a way to use the method to go from 4 all the way to 7. Just some of the fixes would be to change Rails version to 5 and 6. Author even said that it’s not a dogmatic thing, there is no point in interpreting it that way, just because OP does not include a couple of sentences on “you totally should upgrade to version 5 before going to 7”. It’s implied.
- marcosdumay 3y agoYou and the GP talking in universals... It's amazing that exist people whose personal experience alone isn't enough to think that way. But well, just to be clear, no all libraries do not agree on any way of managing updates.