| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Since the Rack::Lock still exists in development,
let's provide a way to disable it explicitly.
|
|\
| |
| | |
New 404, 422, 500 pages, they are more stylish and bring ruby essence…
|
| |
| |
| |
| |
| |
| | |
moving changelog note to unreleased section
New beauty pages(404, 422, 500)
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes you want to create a table without an associated model and
test, which is also not a join table. With this commit, you can now
do that.
Example:
rails g migration create_posts title:string
or
rails g migration CreatePosts title:string
This commit also moves the template the model generator uses for the
migration to the migration templates folder, as it seems a more
sensible place for it now that it is shared code.
|
| |
|
|
|
|
| |
Closes #9386
|
|\
| |
| | |
Use less hyperbole in the language re: allowed parameters
|
| | |
|
|/ |
|
|\
| |
| | |
Change default root route helper
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Ignore block comments and calculates number of functions.
|
|\
| |
| | |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we removed script/rails and introduced bin/rails, we accidentally
introduced a regression. If you install Rails 4 as a gem, then try to do
something in a Rails 3 application:
$ rails g
This will throw the 'please type rails new foo' message rather than the
proper generator documentation message. This is because older apps don't
have bin/rails.
Therefore, we now *prefer* bin/rails, but still search for script/rails,
and exec the one we find.
|
|
|
| |
Better comment for database_configuration method
|
|
|
| |
Changed comment that referenced the property #database_configuration_file, now it's paths["config/database"]
|
| |
|
|\
| |
| | |
move config.assets.precompile into config/application.rb
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
| |
make connection_url_to_hash a class method
This als prevents loading database.yml if it doesn't exist
but DATABASE_URL does
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Whilst autoloading is known to be not threadsafe, leaving it in place
is a softer solution than failing hard when an application is deployed.
Many older applications will have paths added to `autoload_paths` and
ideally these should be eagerly loaded to be threadsafe. However one
of these paths is quite often lib which could lead to unintended
consequences due to the 'junk drawer' nature of this directory.
Developers should refrain from adding paths to `autoload_paths` or
`eager_load_paths` and use custom folders inside app for code that
needs to be eagerly loaded and use `require` or `require_dependency`
to explicitly load code from other locations.
|
|
|
|
|
|
|
|
|
|
|
| |
Because of the possibility of lib being unintentionally eager loaded
it's been agreed that we'll leave autoload paths and eager load paths
separate for Rails 4.0.
This reverts commit 0757b3388ffe4f44b60de950d40e18ef05055931.
Conflicts:
railties/CHANGELOG.md
|
| |
|
|
|
|
| |
Thanks @sikachu. :sweat_smile:
|
|
|
|
|
|
| |
Print a message in both `rake routes` and at GET "/rails/info/routes"
that lets you know you have no routes defined, as well as linking to the
Rails Guide on the topic.
|
|
|
|
| |
see: https://github.com/blog/1406-namespaced-gists
|
|
|
|
|
|
| |
User should know that he can overwrite the previous migration. This
comes in handy especially when generating models which were previously
created then removed.
|
|
|
|
| |
Add test:all and test:all:db rake tests to speed up full test runs.
|