Excise generated whitespace. Closes #10017 [Tim Pope]

git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@8055 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
This commit is contained in:
Jeremy Kemper 2007-10-29 21:40:23 +00:00
parent bef071dd0b
commit 3ba23348de
4 changed files with 3 additions and 21 deletions

View File

@ -1,2 +1,2 @@
Use this README file to introduce your application and point to useful places in the API for learning more.
Run "rake doc:app" to generate API documentation for your models, controllers, helpers, and libraries.
Run "rake doc:app" to generate API documentation for your models, controllers, helpers, and libraries.

View File

@ -7,4 +7,4 @@ class ApplicationController < ActionController::Base
# See ActionController::RequestForgeryProtection for details
# Uncomment the :secret if you're not using the cookie session store
protect_from_forgery # :secret => '<%= app_secret %>'
end
end

View File

@ -4,7 +4,7 @@ class <%= migration_name %> < ActiveRecord::Migration
<% for attribute in attributes -%>
t.<%= attribute.type %> :<%= attribute.name %>
<% end %>
t.timestamps
t.timestamps
end
end

View File

@ -1,18 +0,0 @@
Description:
The resource generator creates an empty model and controller for use in a REST-friendly, resource-oriented
application. Say you want to a resource called post. Normally, you could just call "script/generate model post" and
"script/generate controller posts". This generator basically just collapses these two generators into one step.
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 post" will generate a Post model and a PostsController and will be intended
for URLs like /posts and /posts/45.
As additional parameters, the generator will take attribute pairs described by name and type. These attributes will
be used to prepopulate the migration to create the table for the model and give you a set of predefined fixture.
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 working with the resource.
Examples:
./script/generate resource post
./script/generate resource post title:string created_on:date body:text published:boolean
./script/generate resource purchase order_id:integer created_at:datetime amount:decimal