TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Fix USAGE typo in resource generator. Closes #8406.

Browse Source 
git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6795 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
This commit is contained in:
Jeremy Kemper 2007-05-20 23:25:18 +00:00
parent ae2db50873
commit 7232cb705a
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
railties/lib/rails_generator/generators/components/resource/USAGE
View File

@ -1,29 +1,29 @@
Description: Description:
The resource generator creates an empty model, controller, and functional The resource generator creates an empty model, controller, and functional
suitable for inclusion in a REST-like, resource-oriented application. test suitable for a RESTful, resource-oriented application.
The generator takes the name of the model as its first argument. This The generator takes the name of the model as its first argument. This
model name is then pluralized to get the controller name. So "resource model name is then pluralized to get the controller name. So "resource
post" will generate a Post model and a PostsController and will be post" will generate a Post model and a PostsController and will be
intended for URLs like /posts and /posts/45. intended for URLs like /posts and /posts/45.
As additional parameters, the generator will take attribute pairs As additional parameters, the generator will take attribute pairs
described by name and type. These attributes will be used to described by name and type. These attributes will be used to
prepopulate the migration to create the table for the model. For prepopulate the migration to create the table for the model. For
example, "resource post title:string created_on:date body:text example, "resource post title:string created_on:date body:text
published:boolean" will give you a Post model with those four attributes. published:boolean" will give you a Post model with those four attributes.
You don't have to think up all attributes up front, but it's a good You don't have to think up all attributes up front, but it's a good
idea of adding just the baseline of what's needed to start really idea of adding just the baseline of what's needed to start really
working with the resource. working with the resource.
The generator also adds an appropriate map.resources declaration to The generator also adds an appropriate map.resources declaration to
your config/routes.rb file, hooking up the rules that'll point URLs to your config/routes.rb file, hooking up the rules that'll point URLs to
this new resource. this new resource.
Unlike the scaffold generator, the resource generator does not Unlike the scaffold generator, the resource generator does not
create views or add any methods to the generated controller. create views or add any methods to the generated controller.
Examples: Examples:
./script/generate resource post # no attributes ./script/generate resource post # no attributes
./script/generate resource post title:string created_on:date body:text published:boolean ./script/generate resource post title:string created_on:date body:text published:boolean