mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
fixed typos
This commit is contained in:
parent
ae7910fad4
commit
e9732c75a8
1 changed files with 6 additions and 6 deletions
|
@ -48,7 +48,7 @@ Title: Rails debugging guide
|
|||
|
||||
h4. +to_yaml+
|
||||
|
||||
Displaying an instance variable, or any other object or method, in yaml format can be achieved this way:
|
||||
Displaying an instance variable, or any other object or method, in YAML format can be achieved this way:
|
||||
|
||||
<html>
|
||||
<%= simple_format @post.to_yaml %>
|
||||
|
@ -122,7 +122,7 @@ It can also be useful to save information to log files at runtime. Rails maintai
|
|||
|
||||
h4. What is the Logger?
|
||||
|
||||
Rails makes use of Ruby's standard +logger+ to write log information. You can also substitute another logger such as +Log4R+ if you wish.
|
||||
Rails makes use of Ruby's standard +logger+ to write log information. You can also substitute another logger such as +Log4r+ if you wish.
|
||||
|
||||
You can specify an alternative logger in your +environment.rb+ or any environment file:
|
||||
|
||||
|
@ -178,7 +178,7 @@ class PostsController < ApplicationController
|
|||
|
||||
if @post.save
|
||||
flash[:notice] = 'Post was successfully created.'
|
||||
logger.debug "The post was saved and now is the user is going to be redirected..."
|
||||
logger.debug "The post was saved and now the user is going to be redirected..."
|
||||
redirect_to(@post)
|
||||
else
|
||||
render :action => "new"
|
||||
|
@ -204,7 +204,7 @@ Post should be valid: true
|
|||
Post Create (0.000443) INSERT INTO "posts" ("updated_at", "title", "body", "published",
|
||||
"created_at") VALUES('2008-09-08 14:52:54', 'Debugging Rails',
|
||||
'I''m learning how to print in logs!!!', 'f', '2008-09-08 14:52:54')
|
||||
The post was saved and now is the user is going to be redirected...
|
||||
The post was saved and now the user is going to be redirected...
|
||||
Redirected to #<Post:0x20af760>
|
||||
Completed in 0.01224 (81 reqs/sec) | DB: 0.00044 (3%) | 302 Found [http://localhost/posts]
|
||||
</shell>
|
||||
|
@ -601,7 +601,7 @@ There are some settings that can be configured in ruby-debug to make it easier t
|
|||
|
||||
You can see the full list by using +help set+. Use +help set _subcommand_+ to learn about a particular +set+ command.
|
||||
|
||||
TIP: You can include any number of these configuration lines inside a +.rdebugrc+ file in your HOME directory. ruby-debug will read this file every time it is loaded. and configure itself accordingly.
|
||||
TIP: You can include any number of these configuration lines inside a +.rdebugrc+ file in your HOME directory. ruby-debug will read this file every time it is loaded and configure itself accordingly.
|
||||
|
||||
Here's a good start for an +.rdebugrc+:
|
||||
|
||||
|
@ -615,7 +615,7 @@ h3. Debugging Memory Leaks
|
|||
|
||||
A Ruby application (on Rails or not), can leak memory - either in the Ruby code or at the C code level.
|
||||
|
||||
In this section, you will learn how to find and fix such leaks by using Bleak House and Valgrind debugging tools.
|
||||
In this section, you will learn how to find and fix such leaks by using tools such as BleakHouse and Valgrind.
|
||||
|
||||
h4. BleakHouse
|
||||
|
||||
|
|
Loading…
Reference in a new issue