aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/lib
diff options
context:
space:
mode:
authorSebastian Martinez <sebastian@wyeworks.com>2011-05-09 22:21:00 -0300
committerSebastian Martinez <sebastian@wyeworks.com>2011-05-09 22:21:00 -0300
commited8962c821ac3e1ff32d692c57703b6851c92b18 (patch)
tree205c2fe61be4216190e18b4b3136e99d3674cf5f /actionpack/lib
parent56a7db6ea8e3a64df836b580ac9499b3de4753f0 (diff)
downloadrails-ed8962c821ac3e1ff32d692c57703b6851c92b18.tar.gz
rails-ed8962c821ac3e1ff32d692c57703b6851c92b18.tar.bz2
rails-ed8962c821ac3e1ff32d692c57703b6851c92b18.zip
more fixed-fonts here
Diffstat (limited to 'actionpack/lib')
-rw-r--r--actionpack/lib/action_dispatch/routing/mapper.rb46
1 files changed, 23 insertions, 23 deletions
diff --git a/actionpack/lib/action_dispatch/routing/mapper.rb b/actionpack/lib/action_dispatch/routing/mapper.rb
index ed050b7c6a..873f78ec74 100644
--- a/actionpack/lib/action_dispatch/routing/mapper.rb
+++ b/actionpack/lib/action_dispatch/routing/mapper.rb
@@ -335,7 +335,7 @@ module ActionDispatch
#
# [:on]
# Shorthand for wrapping routes in a specific RESTful context. Valid
- # values are :member, :collection, and :new. Only use within
+ # values are +:member+, +:collection+, and +:new+. Only use within
# <tt>resource(s)</tt> block. For example:
#
# resource :bar do
@@ -352,7 +352,7 @@ module ActionDispatch
#
# [:constraints]
# Constrains parameters with a hash of regular expressions or an
- # object that responds to #matches?
+ # object that responds to <tt>#matches?</tt>
#
# match 'path/:id', :constraints => { :id => /[A-Z]\d{5}/ }
#
@@ -373,7 +373,7 @@ module ActionDispatch
# See <tt>Scoping#defaults</tt> for its scope equivalent.
#
# [:anchor]
- # Boolean to anchor a #match pattern. Default is true. When set to
+ # Boolean to anchor a <tt>#match</tt> pattern. Default is true. When set to
# false, the pattern matches any request prefixed with the given path.
#
# # Matches any request starting with 'path'
@@ -517,15 +517,15 @@ module ActionDispatch
# You may wish to organize groups of controllers under a namespace.
# Most commonly, you might group a number of administrative controllers
# under an +admin+ namespace. You would place these controllers under
- # the app/controllers/admin directory, and you can group them together
- # in your router:
+ # the <tt>app/controllers/admin</tt> directory, and you can group them
+ # together in your router:
#
# namespace "admin" do
# resources :posts, :comments
# end
#
# This will create a number of routes for each of the posts and comments
- # controller. For Admin::PostsController, Rails will create:
+ # controller. For <tt>Admin::PostsController</tt>, Rails will create:
#
# GET /admin/posts
# GET /admin/posts/new
@@ -536,7 +536,7 @@ module ActionDispatch
# DELETE /admin/posts/1
#
# If you want to route /posts (without the prefix /admin) to
- # Admin::PostsController, you could use
+ # <tt>Admin::PostsController</tt>, you could use
#
# scope :module => "admin" do
# resources :posts
@@ -546,7 +546,7 @@ module ActionDispatch
#
# resources :posts, :module => "admin"
#
- # If you want to route /admin/posts to PostsController
+ # If you want to route /admin/posts to +PostsController+
# (without the Admin:: module prefix), you could use
#
# scope "/admin" do
@@ -559,7 +559,7 @@ module ActionDispatch
#
# In each of these cases, the named routes remain the same as if you did
# not use scope. In the last case, the following paths map to
- # PostsController:
+ # +PostsController+:
#
# GET /admin/posts
# GET /admin/posts/new
@@ -587,7 +587,7 @@ module ActionDispatch
#
# === Examples
#
- # # route /posts (without the prefix /admin) to Admin::PostsController
+ # # route /posts (without the prefix /admin) to <tt>Admin::PostsController</tt>
# scope :module => "admin" do
# resources :posts
# end
@@ -597,7 +597,7 @@ module ActionDispatch
# resources :posts
# end
#
- # # prefix the routing helper name: sekret_posts_path instead of posts_path
+ # # prefix the routing helper name: +sekret_posts_path+ instead of +posts_path+
# scope :as => "sekret" do
# resources :posts
# end
@@ -679,12 +679,12 @@ module ActionDispatch
# resources :posts
# end
#
- # # maps to Sekret::PostsController rather than Admin::PostsController
+ # # maps to <tt>Sekret::PostsController</tt> rather than <tt>Admin::PostsController</tt>
# namespace :admin, :module => "sekret" do
# resources :posts
# end
#
- # # generates sekret_posts_path rather than admin_posts_path
+ # # generates +sekret_posts_path+ rather than +admin_posts_path+
# namespace :admin, :as => "sekret" do
# resources :posts
# end
@@ -846,20 +846,20 @@ module ActionDispatch
# You may wish to organize groups of controllers under a namespace. Most
# commonly, you might group a number of administrative controllers under
# an +admin+ namespace. You would place these controllers under the
- # app/controllers/admin directory, and you can group them together in your
- # router:
+ # <tt>app/controllers/admin</tt> directory, and you can group them together
+ # in your router:
#
# namespace "admin" do
# resources :posts, :comments
# end
#
- # By default the :id parameter doesn't accept dots. If you need to
- # use dots as part of the :id parameter add a constraint which
+ # By default the +:id+ parameter doesn't accept dots. If you need to
+ # use dots as part of the +:id+ parameter add a constraint which
# overrides this restriction, e.g:
#
# resources :articles, :id => /[^\/]+/
#
- # This allows any character other than a slash as part of your :id.
+ # This allows any character other than a slash as part of your +:id+.
#
module Resources
# CANONICAL_ACTIONS holds all actions that does not need a prefix or
@@ -975,7 +975,7 @@ module ActionDispatch
# resource :geocoder
#
# creates six different routes in your application, all mapping to
- # the GeoCoders controller (note that the controller is named after
+ # the +GeoCoders+ controller (note that the controller is named after
# the plural):
#
# GET /geocoder/new
@@ -1024,7 +1024,7 @@ module ActionDispatch
# resources :photos
#
# creates seven different routes in your application, all mapping to
- # the Photos controller:
+ # the +Photos+ controller:
#
# GET /photos/new
# POST /photos
@@ -1107,7 +1107,7 @@ module ActionDispatch
#
# === Examples
#
- # # routes call Admin::PostsController
+ # # routes call <tt>Admin::PostsController</tt>
# resources :posts, :module => "admin"
#
# # resource actions are at /admin/posts.
@@ -1151,7 +1151,7 @@ module ActionDispatch
# end
#
# This will enable Rails to recognize paths such as <tt>/photos/search</tt>
- # with GET, and route to the search action of PhotosController. It will also
+ # with GET, and route to the search action of +PhotosController+. It will also
# create the <tt>search_photos_url</tt> and <tt>search_photos_path</tt>
# route helpers.
def collection
@@ -1175,7 +1175,7 @@ module ActionDispatch
# end
#
# This will recognize <tt>/photos/1/preview</tt> with GET, and route to the
- # preview action of PhotosController. It will also create the
+ # preview action of +PhotosController+. It will also create the
# <tt>preview_photo_url</tt> and <tt>preview_photo_path</tt> helpers.
def member
unless resource_scope?