| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Add more info on working with postgres ENUM type
|
| | |
|
|\ \
| | |
| | | |
Remove check for caller_locations in Rails::Engine
|
| |/
| |
| |
| | |
This is no longer necessary, as the minimum version requirement for Ruby is 2.2.2, and the `caller_locations` feature was added in Ruby 2.0.0. Since Rails no longer supports pre 2.0 versions of Ruby, there is no need to check first if the Kernel does respond to `caller_locations`. The answer is: yes it does.
|
|\ \
| | |
| | | |
Docs: Update options for add_reference
|
| | |
| | |
| | | |
[ci skip]
|
|\ \ \
| | | |
| | | | |
ActiveJob - log enqueued message only after the job was successfully enqueued
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
action mailer test cases protected method can be `# :nodoc:` [ci skip]
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
[ci skip] Fix ActiveRecord::Relation#update documentation
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* before
```
people = Person.where(group: 'expert')
people.update(group: 'masters')
Note: Updating a large number of records will run a
UPDATE query for each record, which may cause a performance
issue. So if it is not needed to run callbacks for each update, it is
preferred to use <tt>update_all</tt> for updating all records using
a single query.
```
* after
```
people = Person.where(group: 'expert')
people.update(group: 'masters')
```
Note: Updating a large number of records will run an
UPDATE query for each record, which may cause a performance
issue. So if it is not needed to run callbacks for each update, it is
preferred to use <tt>update_all</tt> for updating all records using
a single query.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[ci skip] Fix #seconds_since_midnight documentation output it will al…
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | | |
return floating pointnumber
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Update text on CSS Injection
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[skip ci]
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix Time.now format in documentation [ci skip]
|
| | |/ / / /
| |/| | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Use #current instead of #now to prevent zone issues and use new ruby …
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
application's time zone
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Suppress warnings of `assigned but unused variable`
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
`alias :migrations_path= :migrations_paths=`, so
`migrations_path = some_string` is correct.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reverts commit 4147ab730e807f622e5260a5f876749ff41fef26.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
documentations [ci skip]
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* add `end` to end of class definition
* add a blank line between explanation and example code
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[ci skip]
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Introduce `Headers#add`. Move `Response#add_header` upstream.
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* Introduce `ActionDispatch::Http::Headers#add` to add a value to
a multivalued header.
* Move `Response#add_header` upstream: https://github.com/rack/rack/pull/957
* Match upstream `Response#have_header?` -> `#has_header?` name change.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
fixes for warnings and circular require
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This reverts commit 37423e4ff883ad5584bab983aceb4b2b759a1fd8.
Jeremy is right that we shouldn't remove this. The fact is that many
engines are depending on this middleware to be in the default stack.
This ties our hands and forces us to keep the middleware in the stack so
that engines will work. To be extremely clear, I think this is another
smell of "the rack stack" that we have in place. When manipulating
middleware, we should have meaningful names for places in the req / res
lifecycle **not** have engines depend on a particular constant be in a
particular place in the stack. This is a weakness of the API that we
have to figure out a way to address before removing the constant.
As far as timing attacks are concerned, we can reduce the granularity
such that it isn't useful information for hackers, but is still useful
for developers.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Wrong usage of 'a' in docs fixed [ci skip]
|
| | |_|/ / / /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add Singleton in NullMutationTracker class
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
to reduce allocation of same object
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Fixed deprecated string to specify the middleware [ci skip]
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
morgoth/support-array-in-assert_enqueued_jobs-for-only-option
Support passing array to `assert_enqueued_jobs` in `:only` option
|
|/ / / / / / |
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
use class to specify the middleware [ci skip]
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
using string for middleware class names is deprecated in 83b767cef90abfc4c2ee9f4b451b0215501fae9a
|