| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / / |
|
|/ / |
|
| | |
|
|/
|
|
|
|
|
|
| |
The deprecation rake task is no longer useful because the deprecated
methods have already been removed.
The method for silencing stderr has been removed since it was only
useful for `rake test:uncommitted` which was deprecated and removed.
|
| |
|
|
|
|
|
| |
The `rake test:recent` and `rake test:uncommitted` tasks were
deprecated and are now being removed.
|
|\
| |
| |
| |
| | |
Conflicts:
guides/source/layout.html.erb
|
| |
| |
| |
| | |
Add a mention about the helper's test file generated invoking the
controller generator in the USAGE file
|
| | |
|
|\ \
| | |
| | | |
Make "rails dbconsole" work with activerecord-postgis-adapter
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
In #11088, `#to_a` was added to remove a deprecation around using
`#all`. I merged, but it really should have been `#scoped` instead, as
that's the preferred replacement.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Remove the mention about this command in the rails command's help
message and remove the "t" alias related to it.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
jetthoughts/10428_bug_with_config_assets_precompile
#10428: Added tests for config.assets.precompile
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Tests for bug in sprocket-rails:
do not use value of configuration options
which changed after environment loaded
|
| | | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The comment on the +env_config+ method is repetitive, likely to get
outdated, and provides no useful information which cannot be gleamed
from the code. I'm therefore removing it. I'm also refactoring the check
for the presence of a secret_token in the configuration.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 7098d6c9ab28931acc9562a00037567609f9e529, reversing
changes made to 9ec2e2ee91568af24e09760a6de2890b89c33f56.
This make some tests fail /cc @wangjohn
|
|\ \ \
| | | |
| | | | |
Creating a class to build the default middleware stack.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A lot of logic for building the default middleware stack is currently
kept in Application class, but this can be encapsulated and made more
modular by being moved to its own class. Also refactored a couple of the
helper methods.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Removing a repetitive comment and refactoring the Application class in Railties
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Railties.
The comment on the +env_config+ method is repetitive, likely to get
outdated, and provides no useful information which cannot be gleamed
from the code. I'm therefore removing it. I'm also refactoring the check
for the presence of a secret_token in the configuration.
|
|\ \ \ \
| | | | |
| | | | | |
Calls to the application constant have been refactored
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Rails.application when drawing routes and creating other configurations
on the application.
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Is it more suitable that using ```<th colspan="3">``` instead of three empty ```<th>```? It is simple, but what i am missing about it?
Change repetitive th tags to use colspan attribute
Update CHANGELOG.md
Update CHANGELOG.md
|
| | | | |
|
| |_|/
|/| | |
|
|/ /
| |
| |
| |
| |
| |
| | |
1. Used ActiveSupport::Autoload to dry-up the autoload definitions.
2. Used ActiveSupport's delegate to dry up the application proxied
attributes.
3. Did a little white space change on Rails.groups.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Conflicts:
railties/test/application/loading_test.rb
|
| | |
|
| |
| |
| |
| |
| | |
more agnostic Rails.application syntax. This means tests will be more
portable, and won't rely on the existence of a particular subclass.
|
| |
| |
| |
| | |
all directives
|
| |
| |
| |
| | |
particular controller to search for in rake routes.
|
| |
| |
| |
| | |
environment works correctly.
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | | |
Fixes bug 10628.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, ActiveModel is only loaded by ActiveRecord. If you skip ActiveRecord, ActiveModel will not be required (or even autoloaded) and including `ActiveModel::Model` into a plain Ruby class will raise `NameError`.
To reproduce this:
- create a new app with `rails new my_app -O`
- create a Ruby class that includes `ActiveModel::Model` in `app/models`
- load up a Rails console and try to do anything with the class :-)
Since ActionPack relies so heavily on the ActiveModel API, this should probably be considered a dependency of the app. Another possibility would be to make it a dependency of ActionController.
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| |_|/
|/| | |
|