-
-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rails 4.2 Support #607
Comments
Ugh, this is why I've wanted to get rid of Does |
Yup. |
There are two failing specs under Rails 4.2.0.beta1.
I'm going to see if I can suss out the first issue today and submit a PR |
@petergoldstein did you ever adance on this? The only one still failing is |
I've been looking at this since late yesterday and have isolated the spec failure to some behavior I can't explain and suspect is a bug in Rails. When the model's table has a You can reproduce this by editing add_column :restaurants, :type, :string and then running BUNDLE_GEMFILE=gemfiles/Gemfile.rails-4.2.rb bundle exec ruby -Itest test/history_test.rb -n HistoryTestWithFriendlyFinders#test_should_be_findable_by_old_slugs which will pass. If you comment out the line in the schema, then it will fail. |
Rails has done its usual song and dance and changed the way Model.find works in 4.2, so it's now no longer delegated to the internal relation class, but is its own method, so we solve this by including the finders module in the model class as well as the relation class. Resolves #607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
The friendly_id magic find override module doesn't play nice with Rails STI, which is a problem for Topics and TopicalEvents. For these models, use the new recommended method of finding instances based on their slug, which is to go via the `friendly` scope. Eventually, all code should be updated to use this instead of the magic find override module as it isn't very stable and keeps breaking with new releases of Rails[1]. Doing this is before the upgrade to Rails 4 is complete is going to be hard however, so deferring until later. [1] norman/friendly_id#607
It appears that Rails 4.2.0.beta2 breaks core FriendlyId functionality.
The text was updated successfully, but these errors were encountered: