-
Notifications
You must be signed in to change notification settings - Fork 997
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 5 migration or maybe even 6 now? #1413
Comments
Nothing that I know of. I think it'll take someone to give it a try and see if there are any blockers. |
Well rails 4.2.11 was the last security fix for 4.2. question is if one wants to jump to rails 6 beta directly and skip rails 5. |
Pull-requests are much appreciated, if you want to give it a try :)
man. 21. jan. 2019 kl. 18.19 skrev darix <notifications@github.com>:
Well rails 4.2.11 was the last security fix for 4.2. question is if one
wants to jump to rails 6 beta directly and skip rails 5.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1413 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAkeZ19DZcYFnglPQFlG6Nx-Yf6OnPxks5vFfaqgaJpZM4aLDlg>
.
--
--
Laust Rud Jacobsen
laust@object.io | blog: object.io | skype:object.io | +45 2588 4665
|
Though what I did was just updated Gemfile to 5.2, I found these are the blockers:
|
Thanks for the research @hamadata . Can all three of these changes be made prior to an upgrade? |
- app.config.middleware.use "HoptoadNotifier::Rack"
+ app.config.middleware.use HoptoadNotifier::Rack Though it supresses the fatal error after upgrading to Rails5, but I do not know if it works.
https://blog.bigbinary.com/2016/02/29/rails-5-improves-redirect_to_back-with-redirect-back.html
https://til.hashrocket.com/posts/e7a2880383-rails-5-deprecation-warning-for-controller-tests |
Deprecated usage in controller tests can be sovled with this gem. |
I guess a Rails upgrade would also make it easier to use things like webpacker and therefore maybe to get a new UI. |
what is holding this back?
The text was updated successfully, but these errors were encountered: