| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reduces the number of places which will need to care about single
value or range specific logic as we introduce type casting. The array
handler is only responsible for producing `in` statements.
/cc @mrgilman
[Sean Griffin & Melanie Gilman]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This will allow us to pass the predicate builder into the constructor of
these handlers. The procs had to be changed to objects, because the
`PredicateBuilder` needs to be marshalable. If we ever decide to make
`register_handler` part of the public API, we should come up with a
better solution which allows procs.
/cc @mrgilman
[Sean Griffin & Melanie Gilman]
|
| | |
| | |
| | |
| | |
| | | |
We're accidentally documenting `PredicateBuilder` and `ArrayHandler`
since there's a constant which is missing `# :nodoc:`
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Construction of relations can be a hotspot, we don't want to create one
of these in the constructor. This also allows us to do more expensive
things in the predicate builder's constructor, since it's created once
per AR::Base subclass
|
| | |
| | |
| | |
| | | |
We don't memoize the relation instance
|
|\ \ \ |
|
|/ / / |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
I think we should deprecate this behavior and just error if you tell us
to do a case insensitive comparison for types which are not case
sensitive. Partially reverts 35592307
Fixes #18195
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With rails/coffee-rails#61 (and #17241), the `.coffee` extension is
favoured over `.js.coffee`. Respectively, with rails/sass-rails#271
`.scss` and `.sass` are favoured over `.css.scss` and `.css.sass`.
Let's update the documentation to reflect that.
[ci skip]
|
|\ \
| |/
|/|
| |
| | |
kamipo/dump_default_nil_for_postgresql_uuid_primary_key
Dump the default `nil` for PostgreSQL UUID primary key.
|
|/ |
|
|\
| |
| | |
Fixed warning `possible reference to past scope` from railties
|
|/
|
|
| |
past scope`
|
|\
| |
| | |
Fixed AR warning on ruby 2.2
|
| |
| |
| |
| | |
reference to past scope`
|
|\ \
| | |
| | | |
Targeting 2.2
|
| | | |
|
|\ \ \
| | | |
| | | | |
Remove unnecessary double space
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Remove ActionController::ModelNaming
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The methods in these modules are not used anywhere. They used to be
invoked in polymorphic_routes.rb but their usage was removed in e821045.
What is your opinion about removing these methods?
They do belong to the public API, but in reality their code has already been duplicated to ActionView::ModelNaming, since they are used by methods like `dom_id` and `dom_class` to associated records with DOM elements (in
ActionView).
Please tell me if you think that removing this module is a good idea and,
in that case, if the PR is okay as it is, or you'd rather start by showing
a deprecation message, and remove the module in Rails 5.1.
|
| |/
|/| |
|
|\ \
| |/
|/| |
Check for Rails.env instead of Rails
|
|/
|
|
|
| |
`Rails` constant is added by rails-html-sanitizer leading to bugs in
non-Rails apps using ActiveRecord and ActionMailer
|
|\
| |
| | |
List the Active Support Instrumentation guide in the index (as WIP)
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Fix grammar in Caching with Rails docs
|
| |/ |
|
|/ |
|
|\
| |
| | |
Fix bug in ActionMailer guide.
|
|/
|
|
|
| |
When setting a mailer's default from address, you have to pass a hash
with a `:from` key; you can't pass just an email address.
|
|\
| |
| | |
Add support for Reply-To field in mail_to helper
|
| | |
|
|\ \
| | |
| | | |
Removed unused parameter to cookie serialize method
|
|/ /
| |
| |
| | |
same elsewhere
|
|\ \
| | |
| | |
| | |
| | | |
M7/docs-active_record-update_query_method_docs_with_full_description
Describe full behaviour of Active Record's attribute query methods
|
| | |
| | |
| | |
| | |
| | | |
value is present. [ci skip]
The way Active Record query methods handle numeric values is a special case, and is not part of Rails's standard definition of present. This update attempts to make this more clear in the docs, so that people don't expect Object#present? to return false if used on a number that is zero.
|
| | |
| | |
| | | |
Update Active Record's attribute query methods documentation to clarify that whether an attribute is present is based on Object#present?. This gives people a place to go see what the exact definition of presence is. [ci skip]
|
| | |
| | |
| | |
| | | |
full behaviour. [ci skip]
|
| | | |
|
| | |
| | |
| | |
| | | |
References #18148.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Remove unneeded special case to calculate size for has_many :through
|
| | | |
| | | |
| | | |
| | | |
| | | | |
All cases are properly handled in CollectionAssociation
for all subclasses of this association
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
[ci skip]
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We were ignoring the `default_value?` escape clause in the serialized
type, which caused the default value to always be treated as changed.
Fixes #18169
|