| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Restore missing Gemfile.lock entries
|
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
These lines were lost in https://github.com/rails/rails/commit/12d5c210#diff-e79a60dc6b85309ae70a6ea8261eaf95L191.
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
fix link to `resque` [ci skip]
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
`1-x-stable` branch does not exist, `master` is 1.x branch.
Ref: http://words.steveklabnik.com/rescuing-resque-again
|
|\ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / /
|/| | | | | | | | | |
Always store errors details information with symbols
|
|/ / / / / / / / /
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
When the association is autosaved we were storing the details with
string keys. This was creating inconsistency with other details that are
added using the `Errors#add` method. It was also inconsistent with the
`Errors#messages` storage.
To fix this inconsistency we are always storing with symbols. This will
cause a small breaking change because in those cases the details could
be accessed as strings keys but now it can not.
The reason that we chose to do this breaking change is because `#details`
should be considered a low level object like `#messages` is.
Fix #26499.
[Rafael Mendonça França + Marcus Vieira]
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Reduce array allocation when `where` with passed hash
|
| | |_|_|/ / / / /
| |/| | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
In most case `where` is called with passed hash. In the case
initializing `binds` is unnecessary.
|
|\ \ \ \ \ \ \ \ \
| |_|_|_|_|_|_|_|/
|/| | | | | | | | |
use rails command in restart task test
|
| | |_|_|/ / / /
| |/| | | | | | |
|
|\ \ \ \ \ \ \ \
| |_|_|_|/ / / /
|/| | | | | | | |
Remove unnecessry `alias uniq distinct` for collection association
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | | |
`CollectionAssociation` is internal class and `uniq` is not called.
|
|\ \ \ \ \ \ \
| | |_|_|_|/ /
| |/| | | | | |
[ci skip] Fixed commas according to Oxford comma in rdoc and guides
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Rename variable name that returning `type_for` to `type` from `column`
|
| | |/ / / / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
`column_for` was changed to `type_for` to return `type` object at
36bd52b4. But variable name is still `column`. It is very confusing.
Rename variable name `column` to `type` for readability.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Clear attribute changes after handling locking
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Without this the changes to the lock version column will stick around
even after `touch` returns.
Before:
model.touch
model.changes
# => {"lock_version"=>[0, "1"]}
After:
model.touch
model.changes
# {}
|
|\ \ \ \ \ \ \ \
| | |_|/ / / / /
| |/| | | | | | |
[ci skip] Fix bad examples in rdoc
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
fix formatting of `Cache::Store#fetch` [ci skip]
|
| | |_|/ / / /
| |/| | | | |
| | | | | | |
| | | | | | | |
Single backticks don't work with rdoc.
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Fix small grammar issue introduced in #26382
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
improve error message when include assertions fail
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
assert [1, 3].includes?(2) fails with unhelpful "Asserting failed" message
assert_includes [1, 3], 2 fails with "Expected [1, 3] to include 2" which makes it easier to debug and more obvious what went wrong
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Update ActiveModel::Dirty Doc to be simpler to understand
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Rename test to match what it does
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Commit d270da569 changed the `form_for` API from `:object_name` to `:as`.
It also change the related test body, but not its title, which is changed here.
See https://github.com/rails/rails/commit/d270da569efeabd7cd563028816452236713aa9f#diff-52455f1e82acf12551bc5e7e26b82008
I realize this is a small commit but I was having trouble understanding what
the test was about since there is no "object_name" in the code.
I imagine the same may happen to other developers, therefore this commit.
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
DRYing duplicate methods
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[fixes #26441]
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
fix typo in `add_column` doc [ci skip]
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| |_|_|/ / / / /
|/| | | | | | | |
Update ActiveModel::Dirty Doc [ci skip]
|
|/ / / / / / /
| | | | | | |
| | | | | | | |
Fix potentially misleading example.
|
| | | | | | |
| | | | | | |
| | | | | | | |
* added bug report template for migrations
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
remove useless `gemfile` option
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Rails application for test creates with `--skip-gemfile` option.
https://github.com/rails/rails/blob/master/railties/test/isolation/abstract_unit.rb#L333
Therefore, regardless of the option, Gemfile is not created.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Correct `render text:` deprecation message
|
| | |_|_|/ / / /
| |/| | | | | |
| | | | | | | | |
The default Content-Type is `text/html`, not `text/plain`.
|
|\ \ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
Improve assert_response helper
|
| | |_|_|/ / /
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When the check is failed, print the actual response body if it's not too large.
This could improve productivity when writing new tests.
Before:
```
ThemeEditorIntegrationTest#test_whatever
Expected response to be a <200: ok>, but was a <422: Unprocessable Entity>.
Expected: 200
Actual: 422
```
After:
```
ThemeEditorIntegrationTest#test_whatever
Expected response to be a <200: ok>, but was a <422: Unprocessable Entity>.
Expected: 200
Actual: 422
Response body: {"errors":["Invalid settings object for section '1'"]}
```
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Move comment about disconnecting pool close to comment about preload
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
- These two comments are connected to each other so kept them back to back.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
fix broken generators test
|
| |/ / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Follow up to 92703a9ea5d8b96f30e0b706b801c9185ef14f0e
|
| | | | | | | | |
|
| |_|_|/ / / /
|/| | | | | | |
|