diff options
| -rw-r--r-- | railties/guides/source/getting_started.textile | 4 | ||||
| -rw-r--r-- | railties/guides/source/i18n.textile | 2 | ||||
| -rw-r--r-- | railties/guides/source/routing.textile | 10 | ||||
| -rw-r--r-- | railties/guides/source/testing.textile | 12 |
4 files changed, 14 insertions, 14 deletions
diff --git a/railties/guides/source/getting_started.textile b/railties/guides/source/getting_started.textile index 6a600e801a..7c7f7e889c 100644 --- a/railties/guides/source/getting_started.textile +++ b/railties/guides/source/getting_started.textile @@ -163,7 +163,7 @@ $ cd blog In any case, Rails will create a folder in your working directory called <tt>blog</tt>. Open up that folder and explore its contents. Most of the work in this tutorial will happen in the <tt>app/</tt> folder, but here’s a basic rundown on the function of each folder that Rails creates in a new application by default: -|File/Folder|Purpose| +|_.File/Folder|_.Purpose| |README|This is a brief instruction manual for your application. Use it to tell others what your application does, how to set it up, and so on.| |Rakefile|This file contains batch jobs that can be run from the terminal.| |app/|Contains the controllers, models, and views for your application. You'll focus on this folder for the remainder of this guide.| @@ -327,7 +327,7 @@ NOTE. While scaffolding will get you up and running quickly, the "one size fits The scaffold generator will build 14 files in your application, along with some folders, and edit one more. Here's a quick overview of what it creates: -|File |Purpose| +|_.File |_.Purpose| |app/models/post.rb |The Post model| |db/migrate/20090113124235_create_posts.rb |Migration to create the posts table in your database (your name will include a different timestamp)| |app/views/posts/index.html.erb |A view to display an index of all posts | diff --git a/railties/guides/source/i18n.textile b/railties/guides/source/i18n.textile index c5025eb86b..bb445c0bf7 100644 --- a/railties/guides/source/i18n.textile +++ b/railties/guides/source/i18n.textile @@ -720,7 +720,7 @@ So, for example, instead of the default error message +"can not be blank"+ you c * +count+, where available, can be used for pluralization if present: -| validation | with option | message | interpolation| +|_. validation |_.with option |_.message |_.interpolation| | validates_confirmation_of | - | :confirmation | -| | validates_acceptance_of | - | :accepted | -| | validates_presence_of | - | :blank | -| diff --git a/railties/guides/source/routing.textile b/railties/guides/source/routing.textile index d489568ef4..c26a5cd6ee 100644 --- a/railties/guides/source/routing.textile +++ b/railties/guides/source/routing.textile @@ -131,7 +131,7 @@ map.resources :photos creates seven different routes in your application: -|_.HTTP verb |_.URL |_.controller |_.action |_.used for| +|_.HTTP verb|_.URL |_.controller|_.action |_.used for| |GET |/photos |Photos |index |display a list of all photos| |GET |/photos/new |Photos |new |return an HTML form for creating a new photo| |POST |/photos |Photos |create |create a new photo| @@ -188,7 +188,7 @@ map.resource :geocoder creates six different routes in your application: -|_.HTTP verb |_.URL |_.controller |_.action |_.used for| +|_.HTTP verb|_.URL |_.controller|_.action |_.used for| |GET |/geocoder/new |Geocoders |new |return an HTML form for creating the new geocoder| |POST |/geocoder |Geocoders |create |create the new geocoder| |GET |/geocoder |Geocoders |show |display the one and only geocoder resource| @@ -231,7 +231,7 @@ map.resources :photos, :controller => "images" will recognize incoming URLs containing +photo+ but route the requests to the Images controller: -|_.HTTP verb |_.URL |_.controller |_.action |_.used for| +|_.HTTP verb|_.URL |_.controller|_.action |_.used for| |GET |/photos |Images |index |display a list of all images| |GET |/photos/new |Images |new |return an HTML form for creating a new image| |POST |/photos |Images |create |create a new image| @@ -304,7 +304,7 @@ map.resources :photos, :as => "images" will recognize incoming URLs containing +image+ but route the requests to the Photos controller: -|_.HTTP verb |_.URL |_.controller |_.action |_:used for| +|_.HTTP verb|_.URL |_.controller|_.action |_:used for| |GET |/images |Photos |index |display a list of all photos| |GET |/images/new |Photos |new |return an HTML form for creating a new photo| |POST |/images |Photos |create |create a new photo| @@ -420,7 +420,7 @@ TIP: Further below you'll learn about a convenient shortcut for this construct:< In addition to the routes for magazines, this declaration will also create routes for ads, each of which requires the specification of a magazine in the URL: -|_.HTTP verb |_.URL |_.controller |_.action |_.used for| +|_.HTTP verb|_.URL |_.controller|_.action |_.used for| |GET |/magazines/1/ads |Ads |index |display a list of all ads for a specific magazine| |GET |/magazines/1/ads/new |Ads |new |return an HTML form for creating a new ad belonging to a specific magazine| |POST |/magazines/1/ads |Ads |create |create a new ad belonging to a specific magazine| diff --git a/railties/guides/source/testing.textile b/railties/guides/source/testing.textile index 8129dc34c2..9cf41b7aab 100644 --- a/railties/guides/source/testing.textile +++ b/railties/guides/source/testing.textile @@ -217,7 +217,7 @@ NOTE: +db:test:prepare+ will fail with an error if db/schema.rb doesn't exists. h5. Rake Tasks for Preparing your Application for Testing -|_.Tasks |_.Description| +|_.Tasks |_.Description| |+rake db:test:clone+ |Recreate the test database from the current environment's database schema| |+rake db:test:clone_structure+ |Recreate the test databases from the development structure| |+rake db:test:load+ |Recreate the test database from the current +schema.rb+| @@ -384,7 +384,7 @@ By now you've caught a glimpse of some of the assertions that are available. Ass There are a bunch of different types of assertions you can use. Here's the complete list of assertions that ship with +test/unit+, the testing library used by Rails. The +[msg]+ parameter is an optional string message you can specify to make your test failure messages clearer. It's not required. -|_.Assertion |_.Purpose| +|_.Assertion |_.Purpose| |+assert( boolean, [msg] )+ |Ensures that the object/expression is true.| |+assert_equal( obj1, obj2, [msg] )+ |Ensures that +obj1 == obj2+ is true.| |+assert_not_equal( obj1, obj2, [msg] )+ |Ensures that +obj1 == obj2+ is false.| @@ -413,7 +413,7 @@ h4. Rails Specific Assertions Rails adds some custom assertions of its own to the +test/unit+ framework: -|_.Assertion |_.Purpose| +|_.Assertion |_.Purpose| |+assert_valid(record)+ |Ensures that the passed record is valid by Active Record standards and returns any error messages if it is not.| |+assert_difference(expressions, difference = 1, message = nil) {...}+ |Test numeric difference between the return value of an expression as a result of what is evaluated in the yielded block.| |+assert_no_difference(expressions, message = nil, &block)+ |Asserts that the numeric result of evaluating an expression is not changed before and after invoking the passed in block.| @@ -588,7 +588,7 @@ h5. Additional View-based Assertions There are more assertions that are primarily used in testing views: -|_.Assertion |_.Purpose| +|_.Assertion |_.Purpose| |+assert_select_email+ |Allows you to make assertions on the body of an e-mail. | |+assert_select_rjs+ |Allows you to make assertions on RJS response. +assert_select_rjs+ has variants which allow you to narrow down on the updated element or even a particular operation on an element.| |+assert_select_encoded+ |Allows you to make assertions on encoded HTML. It does this by un-encoding the contents of each element and then calling the block with all the un-encoded elements.| @@ -635,7 +635,7 @@ h4. Helpers Available for Integration tests In addition to the standard testing helpers, there are some additional helpers available to integration tests: -|_.Helper |_.Purpose| +|_.Helper |_.Purpose| |+https?+ |Returns +true+ if the session is mimicking a secure HTTPS request.| |+https!+ |Allows you to mimic a secure HTTPS request.| |+host!+ |Allows you to set the host name to use in the next request.| @@ -732,7 +732,7 @@ h3. Rake Tasks for Running your Tests You don't need to set up and run your tests by hand on a test-by-test basis. Rails comes with a number of rake tasks to help in testing. The table below lists all rake tasks that come along in the default Rakefile when you initiate a Rail project. -|_.Tasks |_.Description| +|_.Tasks |_.Description| |+rake test+ |Runs all unit, functional and integration tests. You can also simply run +rake+ as the _test_ target is the default.| |+rake test:units+ |Runs all the unit tests from +test/unit+| |+rake test:functionals+ |Runs all the functional tests from +test/functional+| |