| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Made the change as per the following text in routing guide:-
"You should put the root route at the top of the file,
because it is the most popular route and should be matched first."
However, if root is best left at bottom. We will change to fix that text
|
| |
| |
| |
| |
| |
| | |
The Gemfile of new application uses ruby 1.9 hashes. Gem method of
generators should use them too. It prevents from mixing two kinds of
syntax in one file.
|
| |
| |
| |
| |
| |
| |
| | |
Using require in development mode will prevent required files from
reloading, even if they're changed. In order to keep namespaced
application_controller reloadable, we need to use require_dependency
instead of require.
|
| |
| |
| |
| |
| |
| |
| | |
Ruby tries to use '-h' as short version of '--header' by default
https://github.com/ruby/ruby/blob/trunk/lib/optparse.rb#L1372-1381.
To force `rails db -h` prints an usage message we should add the `-h`
options explicitly.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rails uses sqlit3 db file with a path relative to the rails root. It
allows to execute server not from rails root only. For example you
can fire `./spec/dummy/script/rails s` to start dummy application
server if you develop some engine gem.
Now the `rails db` command uses relative paths also and you can explore
your dummy db via `./spec/dummy/script/rails db` command.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In development mode, dependencies are loaded dynamically at runtime,
using `const_missing`. Because of that, when one of the constants is
already loaded and `const_missing` is not triggered, user can end up
with unexpected results.
Given such file in an Engine:
```ruby
module Blog
class PostsController < ApplicationController
end
end
```
If you load it first, before loading any application files, it will
correctly load `Blog::ApplicationController`, because second line will
hit `const_missing`. However if you load `ApplicationController` first,
the constant will be loaded already, `const_missing` hook will not be
fired and in result `PostsController` will inherit from
`ApplicationController` instead of `Blog::ApplicationController`.
Since it can't be fixed in `AS::Dependencies`, the easiest fix is to
just explicitly load application controller.
closes #6413
|
|\ \
| |/
|/| |
Fixed DataMapper namings in symbols and constants.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
`class_attribute` already generates instance readers/writers by default,
so there's no need to add delegation methods.
Removes some "method redefined" warnings.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit fixes route inspection in `rake routes`
Before:
foo /foo(.:format) :controller#:action"
After:
foo /foo(.:format) Redirect (301)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reverted changes:
f3482a9 Fix tests in railties
5904295 improve #6318
aed906a prevent using already loaded Gemfile for 'bundle install'
In order to fix this, we need a fix in bundler related to GEM_PATH,
which will allow to run tests properly. I will get this changes back
when it happens.
|
| | |
|
|\ \
| | |
| | | |
Changing the indentation level of the block comment close for Sass
|
| | |
| | |
| | | |
If one wants to use use SASS for application.css.sass the comment block indentation is invalid.
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
actionpack/lib/action_view/helpers/asset_tag_helper.rb
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
AS, closes #6287
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
configuration for active_support and JSON Encoding
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Comment for active_support's option in application.rb
|
| |/ / |
|
|/ / |
|
| |
| |
| |
| | |
according with http://en.wikipedia.org/wiki/Robots_exclusion_standard
|
| |
| |
| |
| |
| |
| |
| | |
Plugin generator crashes when using the --dummy-path option
Code was assuming the application name in `config/application.rb`
was module Dummy.
|
| | |
|
|\ \
| | |
| | | |
Fast path starts the database console without loading the full Rails env
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| | |
closes #4894
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Also make sure to not use default queue consumer with custom queue
implementation. It is up to the new queue implementation to
start / shutdown the consumer.
|
|\ \
| | |
| | | |
Provided fix for calling rake tasks within mountable engines
|
| | | |
|
|\ \ \
| | | |
| | | | |
Cover Rails::DBConsole with tests
|