| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This reverts commit 3eef1c7c5d0c4538efb9e061b6fe68011f0352b1.
The css compressor should be set in sass-rails plugin. Check
https://github.com/rails/sass-rails/commit/339529f9f6433047df6358c0439e6641cb74f045
for the fix.
|
|
|
|
|
|
|
| |
With the new sprockets-rails we need to explicitly set the CSS
compressor.
See https://github.com/rails/sprockets-rails#changes-from-rails-3x
|
|\
| |
| | |
Remove `--builder` option from `rails` command
|
| |
| |
| |
| |
| |
| |
| | |
Ability to use a custom builder by passing `--builder` (or `-b`) has
been removed. Consider using application template instead. See this
guide for more detail:
http://guides.rubyonrails.org/rails_application_templates.html
|
|\ \
| | |
| | | |
remove config.auto_explain_threshold_in_seconds
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We discussed that the auto explain feature is rarely used.
This PR removes only the automatic explain. You can still display
the explain output for any given relation using `ActiveRecord::Relation#explain`.
As a side-effect this should also fix the connection problem during
asset compilation (#9385). The auto explain initializer in the `ActiveRecord::Railtie`
forced a connection.
|
|/ |
|
|
|
|
|
|
|
| |
This reverts commit 304f4d4c25ccabdbf97d37dd7a92a54d0b63a9c9.
As it turns out everything should behave as it did and we don't
need to move this configuration option.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Most application developers shouldn't be adding paths to
`config.autoload_paths` as it won't be eagerly loaded so
remove it from the generated config/application.rb file.
If a developer does want to autoload from paths outside of the app
directory then they should add the path to `config.eager_load_paths`
as these paths are also autoloaded as well.
|
|
|
|
|
|
| |
User should know that he can overwrite the previous migration. This
comes in handy especially when generating models which were previously
created then removed.
|
| |
|
|
|
|
| |
Use 'some' instead of 'a/an'.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Fixes improper database name when creating a new rails app with a '.'
Conflicts:
railties/CHANGELOG.md
|
| |
| |
| |
| |
| |
| | |
application. EG: `rails new something.awesome.com`
Conflicts:
railties/CHANGELOG.md
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 43e14f8ff203c21646f733d35bdde4e68da70a3b, reversing
changes made to bb17a0f085aba40a1952612f6c98b2a5804a1152.
Conflicts:
railties/lib/rails/generators/rails/app/templates/config/application.rb
railties/lib/rails/generators/rails/app/templates/config/initializers/locale.rb
Reason: setting the Time.zone in an after_initialize block can become a
problem for people upgrading, since it's not going to be available when
config/initializers run, and people might be relying on it.
An example that I noticed was with the Chronic gem, for date/time parsing.
It requires us to configure the time class to be Time.zone, and doing
that in an initializer no longer worked with these changes, so reverting
is the safer path for now.
|
|/
|
|
| |
`require 'rubygems'` is already required in Ruby 1.9 or later.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Deprecate #update_attributes in favor of `#update`.
ORMs that implement `Generators::ActiveModel#update_attributes` should change
to `#update`. Scaffold controller generators should change calls like:
@orm_instance.update_attributes(...)
to:
@orm_instance.update(...)
This goes along with the addition of `ActiveRecord::Base#update`,
introduced in cb2bd4aa619d9329c42aaf6d9f8eacc616ce53f4.
|
|\
| |
| | |
Controller scaffold codestyle
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
API. The default scaffold will now just create HTML if the user actively opts out of jbuilder
|
| |
|
| |
|
| |
|
|
|
|
| |
actions.rb:34: warning: instance variable @in_group not initialized
|
| |
|
| |
|
| |
|
|
|
|
| |
Executable scripts are versioned code like the rest of your app. To generate a stub for a bundled gem: 'bundle binstubs unicorn' and 'git add bin/unicorn'
|
|\
| |
| | |
refactor the naming within plugin new generator
|
| |
| |
| |
| |
| |
| | |
Having a method called `full?`, which checks on :full and :mountable
is very confusing. I renamed `full?` to `engine?` and created a `full?`
method that only checks the `:full` option
|
| |
| |
| |
| | |
should read more about the consequences than just toggling a boolean to make best use of it
|
| |
| |
| |
| | |
config/initializers to take effect
|
| |
| |
| |
| |
| |
| |
| | |
* a controller that destroying Weblogs might be WeblogsController
* a controller that indexing Posts might be PostsController
* Post.all returns a Relation
* modernize Model.inspect results
|
| | |
|
| | |
|
| |
| |
| |
| | |
This is very rarely changed and does not deserve to be in application.rb
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
serve as the example
|
| | |
|
| | |
|
| |
| |
| |
| | |
[ci skip]
|