Skip to content
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

Bump less-rails to remove deprecation warnings, fixes #925 #930

Merged
merged 1 commit into from
Jul 11, 2018

Conversation

davidlaprade
Copy link
Contributor

The warning is:

DEPRECATION WARNING: Sprockets method `register_engine` is deprecated.
Please register a mime type using `register_mime_type` then
use `register_compressor` or `register_transformer`.

This problem is really a less-rails error, and is documented in this
issue of that repo:

metaskills/less-rails#122

It was fixed with this PR, merged Oct 2017:

metaskills/less-rails#137

Bumping our less-rails dependency to 3.0.0 will give us the updates in
that PR.

Version 3.0.0 is the next version after 2.8.0, so there are very few
other changes to worry about. You can view all of the less-rails code
changes between 2.8.0 and 3.0.0 here:

metaskills/less-rails@05186eb...7bb14e5

They are almost all test and/or README changes. So this update should be
low risk.

The warning is:

```
DEPRECATION WARNING: Sprockets method `register_engine` is deprecated.
Please register a mime type using `register_mime_type` then
use `register_compressor` or `register_transformer`.
```

This problem is really a less-rails error, and is documented in this
issue of that repo:

metaskills/less-rails#122

It was fixed with this PR, merged Oct 2017:

metaskills/less-rails#137

Bumping our less-rails dependency to 3.0.0 will give us the updates in
that PR.

Version 3.0.0 is the next version after 2.8.0, so there are very few
other changes to worry about.  You can view all of the less-rails code
changes between 2.8.0 and 3.0.0 here:

metaskills/less-rails@05186eb...7bb14e5

They are almost all test and/or README changes. So this update should be
low risk.
@ealymbaev
Copy link

When are you going to merge this PR? It could solve the unwanted warnings issue.

@ThatHurleyGuy
Copy link

Any chance this could get merged and a new release cut? I'd love to see these deprecation warnings get fixed

@seyhunak seyhunak merged commit 98e3c2a into seyhunak:master Jul 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants