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

Respond to deprecation warnings #32

Closed
mattscilipoti opened this issue May 25, 2016 · 0 comments · Fixed by #33
Closed

Respond to deprecation warnings #32

mattscilipoti opened this issue May 25, 2016 · 0 comments · Fixed by #33

Comments

@mattscilipoti
Copy link
Contributor

mattscilipoti commented May 25, 2016

When I run rake, I see:

DEPRECATION WARNING: The configuration option `config.serve_static_assets` has been renamed to `config.serve_static_files` to clarify its role (it merely enables serving everything in the `public` folder and is unrelated to the asset pipeline). The `serve_static_assets` alias will be removed in Rails 5.0. Please migrate your configuration files accordingly. (called from block in <top (required)> at /Users/matt/develop/opensource/bmoreonrails.org/config/environments/test.rb:16)
Run options: --seed 33373

# Running:

DEPRECATION WARNING: You did not specify a value for the configuration option `active_support.test_order`. In Rails 5, the default value of this option will change from `:sorted` to `:random`.
To disable this warning and keep the current behavior, you can add the following line to your `config/environments/test.rb`:

  Rails.application.configure do
    config.active_support.test_order = :sorted
  end

Alternatively, you can opt into the future behavior by setting this option to `:random`. (called from test_order at /Users/matt/.rvm/gems/ruby-2.2.0/gems/activesupport-4.2.0/lib/active_support/test_case.rb:42)
..

Finished in 0.185602s, 10.7757 runs/s, 10.7757 assertions/s.

2 runs, 2 assertions, 0 failures, 0 errors, 0 skips
  • config.serve_static_assets to config.serve_static_files
  • active_support.test_order = :random
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 a pull request may close this issue.

1 participant