kotovalexarian-likes-github
/
rails--rails
mirror of https://github.com/rails/rails.git
1
0
Fork 0
Code Releases Activity

[skip ci] Debugging Rails Guide fixes 

- Fixes:

"we want go deep" -> "we won't go deep"

"to next next line" -> "to the next line"

- Minor improvements in clarity and grammar.

Cheers :)
This commit is contained in:
Jon Atack 2015-08-15 23:59:01 +02:00
parent 15f3cc8119
commit 94a0c1c584
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
guides/source/debugging_rails_applications.md
View File

@ -619,13 +619,15 @@ Processing by ArticlesController#index as HTML
(byebug) (byebug)
``` ```
If we use `next`, we want go deep inside method calls. Instead, byebug will go If we use `next`, we won't go deep inside method calls. Instead, `byebug` will
to the next line within the same context. In this case, this is the last line of go to the next line within the same context. In this case, it is the last line
the method, so `byebug` will jump to next next line of the previous frame. of the current method, so `byebug` will return to the next line of the caller
+method.
``` ```
(byebug) next (byebug) next
Next went up a frame because previous frame finished
Next advances to the next line (line 6: `end`), which returns to the next line
of the caller method:
[4, 13] in /PathTo/project/test_app/app/controllers/articles_controller.rb [4, 13] in /PathTo/project/test_app/app/controllers/articles_controller.rb
4: # GET /articles 4: # GET /articles
@ -642,8 +644,8 @@ Next went up a frame because previous frame finished
(byebug) (byebug)
``` ```
If we use `step` in the same situation, we will literally go to the next Ruby If we use `step` in the same situation, `byebug` will literally go to the next
instruction to be executed. In this case, Active Support's `week` method. Ruby instruction to be executed -- in this case, Active Support's `week` method.
``` ```
(byebug) step (byebug) step