Generating stubs for helper tests is overly specific. Most helpers should simply be tested as part of the view thats using them. If you need something beyond that, you can add a test yourself for them
Change the production log level default from :info to :debug. All production apps I have ever worked with has done this. Let us reflect that default. You often want those SQL quieries to be able to debug issues in production
Stubs are no longer generated for helpers, so dont test for it
Update docs to reflect that helper stubs are no longer generated
A few more tests asserting the presence of helper test stubs
Using no_result_var in Journey's parser generator

Previously the generated parser had an intermediate local variable
`result` that really useful if you're building up a stateful object but
Journey always discards the result argument to the reduce functions.

This produces a simpler parser for anybody who actually wants to read
the thing.

Sadly, there's no real performance speedup with this change.
Merge pull request #16386 from JackDanger/journey-no-result-var

Using no_result_var in Journey's parser generator
Pull in the custom configuration concept from dhh/custom_configuration
Merge branch 'master' of github.com:rails/rails
Add suggestion as to how you can app the the assets load path
Explain why we use asset digests, not what a setter does