-
Notifications
You must be signed in to change notification settings - Fork 133
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
[fix #122] Avoid Sprockets deprecations #128
Conversation
MustafaZain
commented
Nov 11, 2016
- Use both 'register_engine' and 'register_transformer' in railtie.rb
@MustafaZain works great, thanks! Tests seem to fail though. |
@kreintjes yeah I didn't edit test code but I tried it myself as it's a temp solution for deprecation warning. |
Where does @kreintjes where does this stand? Does there need to be a fork for rails 5 & the less-rails to continue to advance? The game is still posting errors about misusing the sprockets gem months later. |
@Mirv I have no idea. I am no maintainer of either less-rails or rails itself. I simply have an application running Rails with less-rails which I recently updated to Rails 5. I got a bunch of deprecation warnings, and I used @MustafaZain's fork to fix them. It works, but I am afraid his PR will not be merged, as long as the CI does not pass. |
@kreintjes roger - apologies - was following the trail & didn't check to see if you were actually enabled as maintainer! |
@MustafaZain, the test suite is failing because Rails 5 doesn't support any of the Rubies in the current testing matrix. Edit the https://github.com/swanandp/acts_as_list/blob/master/.travis.yml Read the docs on @simi, would you be keen to merge this if @MustafaZain can get the suite up to date and running? Reference: #122 |
55881db
to
42c45e1
Compare
For me this path don't works. I get
Full backtrace:
|
- Use both 'register_engine' and 'register_transformer' in railtie.rb minor fix for Sprockets check version Signed-off-by: Mustafa Zain Eddin <mustafa.m.zeineddin@ieee.org>
That's better :) Now there are just a few failures to deal with. And LOTS! of warnings that could also be dealt with unless they're coming from the gems... |
fixed in 3.0 |