| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Guide'. [ci skip]
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Fix active_record_validations.md document, `:save` for `on:` validation helper was never available
|
| | |_|_|_|/
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
helper was never available
According to the guide, ":save" value for the "on:" validation helper
was available like below
validates :name, presence: true, on: :save
but this was never available according to the implementation of the
valid? method, which is below
# Runs all the validations within the specified context. Returns
+true+ if
# no errors are found, +false+ otherwise.
#
# If the argument is +false+ (default is +nil+), the context is set
to <tt>:create</tt> if
# <tt>new_record?</tt> is +true+, and to <tt>:update</tt> if it is
not.
#
# Validations with no <tt>:on</tt> option will run no matter the
context. Validations with
# some <tt>:on</tt> option will only run in the specified context.
def valid?(context = nil)
context ||= (new_record? ? :create : :update)
output = super(context)
errors.empty? && output
end
So the documentation was always wrong since the PR proposed by
@neerajdotname ( #10287 ) was rejected.
|
| | | | | |
| | | | | |
| | | | | | |
The section was clearly wrong and was just an example about how to use ActiveSupport helpers in Rack/Sinatra
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add note that you must be in the rails app when starting the server
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
server.
This is a response to issue #11731 and is a common mistake for people
newer to rails that try forget to cd into the new rails app after
running rails new.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
i18n guide update: corrected reference to activerecord to instead reference activemodel
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
is in activemodel, not activerecord
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
skip]
Done the following changes:
1. Replace uniq call in example with autosave as uniq is not supported
on has_and_belongs_to_many
2. Add :readonly option to list of supported call as per
[EdgeApi](http://edgeapi.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html#method-i-has_and_belongs_to_many)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
in getting started guide for section 5.6
[ci skip]
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix status codes in document
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
RFC 6585 Additional HTTP Status Codes
http://www.ietf.org/rfc/rfc6585.txt
|
|/ / / / / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
order on the old ones
The previous behavior added a major backward incompatibility since it
impossible to have a upgrade path without major changes on the
application code.
We are taking the most conservative path to be consistent with the idea
of having a smoother upgrade on Rails 4.
We are reverting the behavior for what was in Rails 3.x and,
if needed, we will implement a new API to prepend the order clauses in
Rails 4.1.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Update of 'The Asset Pipeline' guide for Rails 4.
|
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add installation instructions for FreeBSD [ci skip]
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add packages required to setup the rails environment on FreeBSD.
|
|/ / / / / |
|
| |/ / /
|/| | |
| | | |
| | | | |
- Reference #11644
|
|\ \ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
To share a certain logic across other examples, let's add a sample SQL
code generated by the given Ruby code
|
| | | | |
| | | | |
| | | | |
| | | | | |
sorry @robin850.
Thanks @fxn
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 700c6c65bcce17d4c61423ceaef031bcbe203337.
Bot the `sqlite3` and `sqlite3-ruby` gems exist.
https://rubygems.org/gems/sqlite3
https://rubygems.org/gems/sqlite3-ruby
In fact, they both point to the same github repository.
https://github.com/luislavena/sqlite3-ruby
However, the last one hasn't been released since 2011, while the first
one keeps getting regular releases.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Add the packages required on Arch Linux when setting up the development
dependencies
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | | |
for blank?
|
| |/ / /
|/| | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
add the missing middleware in command line guides rake about [ci skip]
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
metal is no longer mentioned on rack guide
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add logging performance [ci skip]
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
|/| | | | |
|
| |/ / /
|/| | | |
|
|\ \ \ \ |
|
| | | | | |
|