It's best to just return text/plain when something has gone terribly
wrong.

Fixes #5660.

Optimize log subscribers to check if the log level is sufficient

Use Rack::Cache middleware only if is in Gemfile

prefix TemplateAssertions ivars.

Closes #7459

resource and resources do no longer modify passed options

this is a patch for #7777.

warning fixed: (...) interpreted as grouped expression

fix broken cache tests

Fix the build (Broken scaffold routes test)

fix cache store test

Pull #7800 broke the build, this should fix it.

Master branch: Fixed generated whitespace in routes when using namespaced resource.

Add a changelog entry for asset aliasing update in sprockets-rails. Supports referencing foo.js as foo/index.js and vice versa.

Fix other assertions that were backwards.

This time I used ack.

fix order of assertions.

Optimize ActiveSupport::Cache::Entry to reduce overhead

Fix changelog entry about sprockets-rails

small refactoring of build_relation in uniqueness

REBASED: fixing assert_template bug when template matches expected, but not ends with

Given Im rendering an template `/layout/hello.html.erb`, assert_template was
passing with any string that matches. This behavior allowed false passing like:

	assert_template "layout"
	assert_template "out/hello"

Now the passing possibilities are:

	assert_template "layout/hello"
	assert_template "hello"

fixing assert_template bug when template matches expected, but not ends with

Cherry Pick Merge: Fixes issue #3849 assert_template false positive

taking redundant test off

prevening incorrect assert_template when rendering with repeated names in path

updating CHANGELOG with bugfix: assert_template false passing

reflection init as 'if' stantment.
column is always the same expression and depends from the changing of attributes

Changed test names to match proper context

Update minitest dependency to ~> 4.0