Match "/users/:id" => "users#show" #Rails 4.0 You should now specify which HTTP verb to respond to with the option :via #Rails 3.2 On routes, the match method will no longer act as a catch-all option. Here’s the commit where this was deprecated. Move it to lib/your_plugin and require it from an initializer on config/initializers.If not, you can reference it from your Gemfile via the :git or :path options. Most plugins should already have a gem version. However, if you still have any code in vendor/plugins, you have 2 options: Most apps were already relying on gems instead of vendored plugins. Therefore, any code in the vendor/plugins directory won’t be loaded. Rails 4 will be removing Rails::Plugins class. Strongly recommended! No More vendor/plugins #More on this can be seen in the Bundler manpages:Ī great resource for 1.8 vs 1.9 changes is the Ruby 1.9 walkthrough by Peter Cooper. Gem 'ruby19-only-gem', :platforms => :ruby_19 It should look something like this: gem 'ruby18-only-gem', :platforms => :ruby_18 Using conditional statements in your Gemfile come in handy for having different gems on each environment until you get it all running on 1.9. Tools like rvm or rbenv help a lot by letting you run multiple versions of Ruby.
Nowadays most gems should be running on 1.9 or have a replacement.
If you’re still on Ruby 1.8.7, things could be a bit more work.
#READY MAKER RAILS UPGRADE#
If you’re using Ruby 1.9.x, the upgrade should be pretty straightforward. Rails 4 is going to target only Ruby 1.9.3 and future versions. We should know about them and be prepared for the upgrade. Some things are going to be completely removed on Rails 4.
0 kommentar(er)
