| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/
|
|
|
|
|
|
| |
plus:
* 80 column formats
* replacing the explanation of the dynamic_form gem with the example
HTML/CSS that Rails scaffolds generate.
|
|\
| |
| |
| |
| | |
Conflicts:
guides/source/active_record_validations.md
|
| | |
|
| |
| |
| |
| | |
skip]
|
| |
| |
| |
| |
| | |
We have three or four different introduction sentences to the guides.
After this commit, we use the same one everywhere.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Some guides work without 'the'. For instance, 'Migrations' or
'Form Helpers.' But when we talk about the asset pipeline, we...
always say 'the asset pipeline.' The guide title should reflect this.
|
| |
| |
| |
| | |
It's obvious that this is a guide.
|
| |
| |
| |
| |
| | |
Other guides that talk about Active Record specific features include the
name of the library in the title, this one should too for consistency.
|
| |
| |
| |
| |
| |
| | |
They're Rails Guides, so obviously we're talking about Rails Form Helpers.
Also, 'helpers' should be capitalized.
|
| |
| |
| |
| | |
It's obvious that this is a guide, and none of the other guides say 'A Guide to'.
|
| |
| |
| |
| | |
It's obvious that the guide is based on this version of Rails, and may not be backwards compatible.
|
| |
| |
| |
| | |
Talked with @fxn about this. Bullet points should have periods at the ends.
|
| |
| |
| |
| | |
The wording of these was a bit off, so I fixed them.
|
| |
| |
| |
| | |
The proper name has a space.
|
| |
| |
| |
| | |
The proper name has a space.
|
| |
| |
| |
| | |
The proper name has a space.
|
| |
| |
| |
| | |
The proper name for the library has a space.
|
| |
| |
| |
| | |
The proper name has a space.
|
| |
| |
| |
| |
| | |
The proper name, as per the documentation guides, is 'Active Record.' I've
updated several references to it as 'ActiveRecord'.
|
| |
| |
| |
| |
| |
| |
| | |
Most of the guides have a few simple sentences describing what they will show
you at the top. This one had a few big paragraphs. I've moved those paragraphs
down to an introductory one, and written a new smaller one for the introduction.
This makes this guide more consistent with the others.
|
| | |
|
| | |
|
| |
| |
| |
| | |
It's properly called "Mac OS X"
|
| |
| |
| |
| | |
This is based on Rails 4, not Rails 3.2.
|
| |
| |
| |
| |
| |
| |
| |
| | |
changed #error_explanation to #errorExplanation"
At least in master the selector is snake case.
This reverts commit ba2fed41613e02bb6cfc46c92ace00abb99ce313.
|
| |
| |
| |
| | |
preformatted text
|
| |
| |
| |
| | |
From https://github.com/lifo/docrails/commit/cfd324b4b68469ba3188e4b7ba8586e59b239693\#commitcomment-2213592
|
| |
| |
| |
| | |
From https://github.com/rails/rails/issues/6161\#issuecomment-10750118
|
| |
| |
| |
| | |
#error_explanation to #errorExplanation
|
| | |
|
| |\
| | |
| | | |
Clarification to ActiveRecord Validations Doc in 7.2 Custom Methods
|
| |/
| |
| | |
In the expiration_date_cannot_be_in_the_past validation method, use `expiration_date.present?` instead of the double negative `!expiration_date.blank?`. Also join the comparisons with `&&` instead of `and`, which could cause unintended consequences.
|
| |
| |
| |
| |
| |
| | |
This reverts commit c94cfdad6388dcdfaf4c10b9e8cee46baf2a7901.
* This is the new 4.0 (master) directory structure
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
* This shows the reader there is a method: and
data: parameters
|
| |
| |
| |
| | |
* No need to give a simple example, as we have a
partial that we create in the blog app
|
| |
| |
| |
| |
| |
| |
| | |
* Rails generate model Post ______ creates the
attr_accessible line for you for any fields
you specify. Changed the section to describe
what this line in the model does.
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Fix #8167 - adding autoloading support for caching
|
|/ /
| |
| |
| | |
(active_support/dependecies.rb) (issue #8167)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chrome, Safari and Firefox serialize Date objects to strings such
as 'Mon May 28 2012 00:00:00 GMT-0700 (PDT)'. When these strings
are parsed the zone is interpreted as 'GMT-0700' which doesn't
exist in the TzInfo list of timezones.
By taking advantage of the improved date/time handling in 1.9.3
we can use `Date._parse` and the `:offset` value which is parsed
correctly.
Three tests were amended to make them pass:
1. test_parse_with_old_date
This needed changing to a different value because the original
value was before EST was adopted so was being changed to a
LMT (Local Mean Time) value after the change. It didn't before
because `DateTime` just has offsets from UTC not timezones.
2. test_parse_should_not_black_out_system_timezone_dst_jump
Changed the implementation of this test as the stubs were
dependent on internal implementation details of the test.
Confirmed that the modified test still failed when the
implementation of `parse` was restored to pre-#5571.
3. test_parse_should_black_out_app_timezone_dst_jump
Ditto.
Closes #5770.
|