| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
I had written the original guide for "A Guide to Testing Rails
Applications". The current documents maintains the same structure and
examples I had drafted albeit with some minor changes to keep up with
newer version of Rails.
Older version which had credits included:
http://guides.rubyonrails.org/v2.3.11/testing.html
Github lifo/docrails History:
https://github.com/rails/rails/commits/ff359af86505b4d317b7467e7f79aa2ef2c5e795/railties/doc/guides/source/testing_rails_applications.txt
|
|\
| |
| | |
remove not used instance variable
|
| | |
|
|\ \
| | |
| | | |
Add a note about edge guides in the feedback section [ci skip]
|
|/ / |
|
|\ \
| | |
| | | |
Performance regression in AR::Base.respond_to?
|
| | |
| | |
| | |
| | |
| | | |
Caches the patterns of ActiveRecord::DynamicMatchers in a class instance
variable.
|
|\ \ \
| | | |
| | | | |
[PG adapter] Use infinity const
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Add examples of AR order method's hash notation to Rails Guide [ci skip]
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
jetthoughts/add_action_controller_bug_report_template
Added bug report template for ActionController
|
| | |/ /
| |/| |
| | | |
| | | | |
[ci skip]
|
|\ \ \ \
| |/ / /
|/| | | |
Stray nodoc causes rest of file not parsed [ci skip]
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Use `Minitest::Test` instead of old `MiniTest::Unit::TestCase` for bug reports template
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
* use `Minitest::Test` instead of deprectaed `MiniTest::Unit::TestCase`
[ci skip]
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[JRuby] Skip few of the ActiveSupport's inflector test cases
Conflicts:
activesupport/test/abstract_unit.rb
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Generalize backtrace check on DelegationError.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Different Ruby implementations present backtraces differently, as
it should be an information consumed by humans.
A better implementation should use data from the error, in this case
returned by NoMethodError#name.
Fixes issues with Rubinius, which presents backtraces differently from
MRI.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Skip tests involving $SAFE on Rubinius, it's not supported.
|
| | | | | | |
|
| | |_|_|/
| |/| | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Escape the message of an exception in debug_exceptions to avoid bad rendering
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Remove set_primary_key, replace with primary_key=
|
|/ / / /
| | | |
| | | | |
First deprecated, now removed: https://github.com/rails/rails/commit/9add7608f1acaa68b025470e7a38901d7e6161ca#activerecord/lib/active_record/attribute_methods/primary_key.rb
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Stop interpreting SQL 'string' columns as :string type.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
SQL doesn't have a string type, and interpreting 'string' as text is
contrary to at least SQLite3's behavior:
"Note that a declared type of 'STRING' has an affinity of NUMERIC, not TEXT."
http://www.sqlite.org/datatype3.html
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Change the wording to explain following methods skip callbacks [ci skip]
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
ensure freeze on Thread freezes locals (#11831)
|
|/ / / / / / |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
statement for it
Refactor of the work done in #11891
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Normalize file parameters in same place as other parameters (ActionDispatch::Http::Parameters#normalize_encode_params)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(ActionDispatch::Http::Parameters#normalize_encode_params)
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
SSE class for ActionController::Live
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This fixes a regression. The documentation said in its introduction
paragraph that the method returns truthy/falsy, but then below it
was said that if there were no arguments you'd get `true` or `false`.
Also when the argument is exactly `false` a singleton is documented
to be returned.
The method was not returning the singletons so it didn't conform to
those special cases.
The best solution here seems to be to just return singletons in all
cases. This solution is backwards compatible. Also, the contract
has been revised because it has no sense that the predicate varies
that way depending on the input. I bet the previous contract was just
an accident, not something mixed on purpose.
Conflicts:
activerecord/lib/active_record/relation/finder_methods.rb
activerecord/test/cases/finder_test.rb
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Follow-up to #11934
|
|\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
xta/clarify_instructions_in_contributing_to_ruby_on_rails
clarify instructions in contributing_to_ruby_on_rails.md for committing ...
[ci skip]
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
skip]
|
| | | | | | |
|