| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
I'm giving @jlsuttles credit on this commit because she gave me the idea
and the actual converted image in 952289aabfb.
|
|\
| |
| | |
Cookie-base session store auto-upgrade
|
| |
| |
| |
| | |
Automatically configure cookie-based sessions to use the best cookie jar given the app's config
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
Fixing some typos/grammar.
|
| |
|
| |
|
|
|
|
| |
in #9904
|
|
|
|
| |
v3 of pull request based on additional feedback from @jeremy
|
| |
|
|
|
|
| |
String
|
|\
| |
| | |
Add #to_s method to VERSION modules
|
| | |
|
| |
| |
| |
| |
| | |
Use the "quit" command instead. This seems to prevents some weirdness on
OS X. See #9761.
|
|/
|
|
|
|
| |
SIGTERM is the correct signal for a graceful exit.
This will hopefully resolve #9761.
|
| |
|
|
|
|
|
|
| |
This reverts commit b7d9d6e2cd5082d269dafbc0316e2107febe1451.
Per discussion with @jeremy and @rubys on Campfire.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* adds password_digest attribute to the migration
* adds has_secure_password to the model
* adds password and password_confirmation password_fields to _form.html
* omits password entirely from index.html and show.html
* adds password and password_confirmation to the controller
* adds unencrypted password and password_confirmation to the controller test
* adds encrypted password_digest to the fixture
|
|
|
|
|
|
| |
Using regexps as arguments without parentheses end up raising:
warning: ambiguous first argument; put parentheses or even spaces
|
|
|
|
|
|
| |
* Unset $RAILS_ENV that got set by abstract_unit to trigger the default.
* split out environment setting since Ruby 1.9.3 doesn't support inline
ENV setting.
|
|
|
|
| |
I forgot to run the test suit after changing the task name. :bomb:
|
|\
| |
| | |
Add `rails test` command to run the test suite
|
| | |
|
| |
| |
| |
| |
| | |
Also, print out deprecation warning for other rake tasks except
`rake test` and `rake` (default)
|
| | |
|
| |
| |
| |
| |
| |
| | |
* `rails test -f` will run the test suites with all fixtures loaded
* New application will now generated without `fixtures :all` line
enabled by default.
|
| |
| |
| |
| |
| | |
Any flags that got set will be passed through to MiniTest::Unit.runner,
such as `-n`, `-s-, and `-v`.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To run the whole test suite:
$ rails test
To run the test file(s):
$ rails test test/unit/foo_test.rb [test/unit/bar_test.rb ...]
To run the test suite
$ rails test [models,helpers,units,controllers,mailers,...]
For more information, see `rails test --help`.
This command will eventually replacing `rake test:*`, and `rake test`
command will actually invoking `rails test` instead.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
| |
This should fix travis. For real this time! This is the one!
The readpartial(100) meant that an earlier assert_stdout could chomp up
the output that a later assert_stdout wants, meaning that the later
assertion fails.
Reading only 1 byte at a time ensure that we don't read any more than is
necessary to verify the assertion.
|
|
|
|
|
|
| |
This should fix travis.
Also ensuring that we don't try to kill when pid is nil.
|
|
|
|
| |
Introduced in be3e10cd26bc8ec29c6474d03a08a8e733108e7d.
|
|
|
|
| |
Thanks @neerajdotname for noticing this bug.
|
|
|
|
|
|
| |
I've also added a proper acceptance test which reproduced the issue.
Closes #9513, #9515.
|
|
|
|
|
| |
Since the Rack::Lock still exists in development,
let's provide a way to disable it explicitly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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
|
|/
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|