| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| |
| |
| |
| |
| |
| | |
Tagged logging for which Rails has support since [3.2](http://guides.rubyonrails.org/3_2_release_notes.html#tagged-logging).
It is trivial & useful but unless somebody explicitly searches API docs, he/she may not know about it.
Hence, I added it in guides.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Changed the title of the 3.5 chapter from "Using the change Method" to
"When to Use the change Method" since the chapter tells the migration
definitions supported by the change method. This fix the duplicate ID in the
document.
I've also changed some of the titles to respect the Guides guidelines.
|
| |
| |
| |
| | |
skip]
|
| |
| |
| |
| | |
erb tag wasn't closed well
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
In chapter 2.4 there was an underscore at the start of the attr_readonly method name,
this underscore was interpreted as the opening of the <em> tag but it wasn't closed.
Worst, the underscore in self.class.serialized_attributes (end of paragraph)
was interpreted as the closing of the <em> tag and not as the name of a method.
|
| | |
|
|/
|
|
|
|
|
|
|
| |
There are two changes:
- Using <ruby> syntax for unicode character routes example instead of
<tt> since it causes single quotes to be transformed into inverted
commas. This makes this required change more eye-catching.
- Using <tt> for the j alias and related helpers as written in the
documentation guidelines.
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
The example is about a Person model, say that "params[:model] would usually be a
hash of all the attributes for the person to create" could be confusing.
I changed to params[:person] since the example is about a Person creation.
|
| |\
| | |
| | | |
Added a bullet for :enable_starttls_auto in the smtp_settings table
|
| | | |
|
| | |
| | |
| | |
| | | |
incorrectly using symbol instead of string
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the text there is a section about how to serve the assets with
far-future headers. The snippet that is proposed doesn't work on Ubuntu
11 (probably others) as mod_expires is not enabled out-of-the-box. I
noted this, and gave an example of how to load mod_expires with a2enmod.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
think that a quoted string will be better as it will automatically
escape double-quotes as well
|
| | |
| | |
| | |
| | |
| | | |
after running, git add .
do not need -a option to git commit
|
| | |
| | |
| | |
| | |
| | | |
Correct :error -> :alert, mention FlashHash class, mention that
you're not limited to notices and alerts, clean up.
|
| | |
| | |
| | |
| | |
| | | |
If the validation of a guide encounters an exception, inform about it
and continue with the loop to validate the rest.
|
| | |
| | |
| | |
| | | |
This rake task was looking for the output folder in the wrong place.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
directory; add exception handling"
This kind of changes should go on a pull request instead.
This reverts commit ecae2f0ef0452f8d333525a6aed58e5ab8d3ccb1.
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
add exception handling
|
| |/ / |
|
| | |
| | |
| | |
| | | |
We need more :heart: in this file. There are a lot of outdated entries.
|
| | | |
|
|/ /
| |
| |
| |
| | |
This functionality will be available from gem
`active_record-session_store` instead.
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 8cb9460437eddde6952fbebbc969203cd4d00294.
Reason: #7377 was merged and it fixes this behavior.
|
| | |
| | |
| | |
| | | |
Fixed bug in the example code. A bit related to rails issue in
https://github.com/rails/rails/issues/3223
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new option allows any Ruby namespace to be registered and set
up for eager load. We are effectively exposing the structure existing
in Rails since v3.0 for all developers in order to make their applications
thread-safe and CoW friendly.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The flag was mainly used to add a Rack::Lock middleware to
the stack, but the only scenario the lock is desired is in
development.
If you are deploying on a not-threaded server, the Rack::Lock
does not provide any benefit since you don't have concurrent
accesses. On the other hand, if you are on a threaded server,
you don't want the lock, since it defeats the purpose of using
a threaded server.
If there is someone out there, running on a thread server
and does want a lock, it can be added to your environment
as easy as: `use Rack::Lock`
|
| | | |
|
| | |
| | |
| | |
| | | |
With a value of "nosniff", this prevents Internet Explorer from MIME-sniffing a response away from the declared content-type.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
AM::Validation#validates: custom exception for :strict option
Conflicts:
activemodel/CHANGELOG.md
|
| | | | |
|
| |/ /
|/| |
| | |
| | | |
This was reverted in https://github.com/rails/rails/commit/fb883318c8b82b3570cee022ddf6886f9052245d
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|